Design pattern suggestion
-
In my site, there is registration fee for membership. Now the registration fee is constant so that i put it in the web config file. Sometimes the client requirement will change by add an option to edit the fee. Then I will prefer to move it into database. So i have to implement the function to get the fee regardless where it resides. Please suggest me which design pattern is suitable for this scenario? Thanks and regards, Majee
-
In my site, there is registration fee for membership. Now the registration fee is constant so that i put it in the web config file. Sometimes the client requirement will change by add an option to edit the fee. Then I will prefer to move it into database. So i have to implement the function to get the fee regardless where it resides. Please suggest me which design pattern is suitable for this scenario? Thanks and regards, Majee
-
The strategy-pattern[^], where you'd create an concrete strategy that can be replaced :)
"Our software isn't released, it escapes leaving a bloody trail of testers behind it."