ASP.Net 2 Application Provider Design Pattern
| Language | English |
| Pages | 15 |
| Size | 611Kb |
| <<< Click here to free download | |
Provider Design Pattern is a new pattern that Microsoft formalized it in ASP.NET Whidbey. The pattern was officially named in the summer of 2002 when Microsoft was designing the new Personalization feature of ASP.NET Whidbey.
Benefits:
1- We won’t explicitly instantiate classes. We let.NET framework take care of instantiating our classes. Framework will be responsible and will manage class instantiation. Framework will re-use classes that have already been instantiated. This will have great effect on memory management of your application.
2- If for some reason you want to change the source of data for your application, for example, moving your database from SQL server to Oracle OR vice versa OR changing your SQL data base server to some sort of XML data source, you will have very easy time to implement this requirement. All you have to do is to replace your existing concrete (implementer) class with a new concrete (implementer) class and inherit from your provider class. That’s all. Your presentation and business logic layer will be kept intact. You don’t have to make any changes into your presentation and business logic layers.
3-Learning Provider Design concept will make it very easy to customize built-in. NET framework providers.
Benefits:
1- We won’t explicitly instantiate classes. We let.NET framework take care of instantiating our classes. Framework will be responsible and will manage class instantiation. Framework will re-use classes that have already been instantiated. This will have great effect on memory management of your application.
2- If for some reason you want to change the source of data for your application, for example, moving your database from SQL server to Oracle OR vice versa OR changing your SQL data base server to some sort of XML data source, you will have very easy time to implement this requirement. All you have to do is to replace your existing concrete (implementer) class with a new concrete (implementer) class and inherit from your provider class. That’s all. Your presentation and business logic layer will be kept intact. You don’t have to make any changes into your presentation and business logic layers.
3-Learning Provider Design concept will make it very easy to customize built-in. NET framework providers.