Thanks for your quick response Scott,
Ok. Here is a brief description on how to profile's data is persisted and
how it is associated with a certain visitor.
** The profile data is persisted in the storage based on the provider you
use. Assume that you use the Default SqlProfileProvider, then, the profile
data is persisted in the sql database.(like other membership/role
provider's data)
** Profile data only associate to a user(through a username string). This
user is determined by membership service. For example, if you use forms
authentication, each authenticated user(according to membership database)
can has his own data in profile db. Profile, in this case, profile do not
take care of cookie, it just check what's the current user. It's the forms
authentication and membership that validate and determine the current
user.
and provide will provide user data depend on the current user's name.
** ASP.NET Profile also support anonymous profile, in this case, it will
generate a random userID for a certain anonymou user(unauthenticated
through forms authentication/membeship). And this id is stored through
cookie, as long as the next time it can get the ID from cookie(still in
unauthenticated mode), it can identify that anonymous user and retrieve
the
correct user data from profile database.
#Profiles In ASP.NET 2.0
http://www.odetocode.com/Articles/440.aspx
Please feel free to let me know if you have questions on any specific part
of the profile.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no
rights.