The Provider Pattern is based on an OO Design Pattern, called the Factory
Pattern.
Here is an example (mine) of the Simple Factory Pattern.
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!126.entry
As far as the Member Provider goes, basically MS provides an abstract class
to handle logins, password.
They also give you one concrete version, called the SqlMembershipProvider.
The good part is that if you don't like the default provider
(SqlMembership), you can write your own version, inheriting from the
abstract base class called MembershipProvider !
Thus if you already have a place where usernames and passwords are kept, you
don't get screwed out of using all the cool 2.0 login controls.
Sometimes people use the abstract version (MembershipProvider)
interchangably with the concrete version (SqlMembershipProvider).
Thus adding some confusion.
4 guys has good explanations of the Membership Provider and the Provider
Model as well.
At my blog post, find the
Here is another link, discussing the ASP.NET 2.0 Provider Model.
line, and follow the link.
"Mike P" <mi*******@gmail.comwrote in message
news:eX**************@TK2MSFTNGP02.phx.gbl...
Can anybody tell me exactly what a provider is? And give an example?
*** Sent via Developersdex http://www.developersdex.com ***
