Hi,
there are many reasons why profile has got attention.
- Provider model: you can specify yourself how the profile data is stored,
and what format it takes. You can also switch to use another datastore than
SQL Server or completely another than database
- Provider model implementation is hidden behind the API e.g data model
change & data changes do not affect the usage
- You can define in web.config what gets stored in the profile (what is
personalized)
- you can also have anonymous profile, and you can migrate that to "full"
one if user authenticates/registers etc
- you can change the data on the fly (via Profile property on the Page)
--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
http://blogs.aspadvice.com/joteke
"cipcip" <pa******@tiscali.it> wrote in message
news:11*********************@g10g2000cwb.googlegro ups.com...
By default profile use sql server xpress provider and probabily, caches
stored data when they are requested for the first time,
So the question is: why we should use profile instead of storyng,
retrieving and caching user data manually from a database?
Is it only for an easier approach of state maintenance, or are there
other advantages?