Re: ASP.NET 2.0 Personalization

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

guess you could do it manually, or using a different provider, but it
would get kind if hairy in that you would need to make sure changes are
propagated back to the original source at some point. If stored in the
cookie (for example) you would have to not only cater for a cookies
limitations, but also save that changed info back to the DB later. Would be
tricky.





"Paul Glavich [MVP ASP.NET]" <glav@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23XHq$5FiFHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
> >> the web servers
> > need to retrieve
> > the profile data from db again?
>
> Yes, and this will happen on demand anyway.
>
> > to read the web parts settings from db then store to another medium?
(like
> > cookie) to reduce
>
> I guess you could do it manually, or using a different provider, but it
> would get kind if hairy in that you would need to make sure changes are
> propagated back to the original source at some point. If stored in the
> cookie (for example) you would have to not only cater for a cookies
> limitations, but also save that changed info back to the DB later. Would
be
> tricky.
>
> --
> - Paul Glavich
> MVP ASP.NET
> http://weblogs.asp.net/pglavich
> ASPInsiders member - http://www.aspinsiders.com
>
>
> "RedHair" <redhair@xxxxxxxxxxxxxxx> wrote in message
> news:uLlDCjffFHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
> > Thanks for your reply.
> > Since the db should be shared between all servers within a web farm,
does
> > it
> > mean that
> > each time when the user requests a user profile property, the web
servers
> > need to retrieve
> > the profile data from db again?
> >
> > By the way, the web parts control works with the personalization
> > mechanism,
> > is it possible
> > to read the web parts settings from db then store to another medium?
(like
> > cookie) to reduce
> > the impact of frequent db access. Those settings is plain text or
> > something
> > else in db?
> >
> >
> > "Paul Glavich [MVP ASP.NET]" <glav@xxxxxxxxxxxxxxxxxxxxxx> ¦b¶l¥ó
> > news:eU0WmXWfFHA.3936@xxxxxxxxxxxxxxxxxxxx ¤¤¼¶¼g...
> >> The personalisation features in ASP.NET 2.0 are all provider driven as
to
> >> where to store data. By default, it will be stored in the Ap_Data
> > directory
> >> as a SqlExpress data file. This can be changed to use a standard SQL
> > Server
> >> provider (provided with ASP.NET V2) and therefore access a SQL Server
> >> independent of the web servers. Obviously this database is shared
between
> >> servers in a web farm, so it should work fine in a web farm scenario.
Use
> >> the ASP.NET Configuration tool is VS.NET to change providers.
> >>
> >> --
> >> - Paul Glavich
> >> MVP ASP.NET
> >
> >> "RedHair" <redhair@xxxxxxxxxxxxxxx> wrote in message
> >> news:eMOp7mUfFHA.484@xxxxxxxxxxxxxxxxxxxxxxx
> >> > How to use user profile within a web farm environment?
> >> >
> >> >
> >>
> >>
> >
> >
>
>



_______________________________________________________________________________
Posted Via Uncensored-News.Com - Accounts Starting At $6.95 - http://www.uncensored-news.com
<><><><><><><> The Worlds Uncensored News Source <><><><><><><><>

.

Relevant Pages