Re: Role Providers Cache
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 17 Aug 2006 21:03:15 -0500
What was the question you were trying to ask? It sounds like you know the
options pretty well.
If you are trying to avoid using session state (always a good idea in my
mind unless it is unavoidable), the cookie does sound like a good idea, but
it could be really big. You could create some sort of compression type of
thing where you have a big bitmap to represent the roles and then just store
the values in the cookie as the representative byte array of the roles. Of
course, then you'd need some code to read and write the cookie in order to
turn those back into friendly representations internally.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Tom" <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:82C8D131-8E7B-482C-A852-192B8E9DFD73@xxxxxxxxxxxxxxxx
If you do not cache role provider to Cookies with the
cacheRolesInCookie="True" in your role provider configuration, will it
default to cache to Session. We may have over 200 roles for some users
and
I am concerned about the size of the cookie but would like the role cached
if
posible. We will be writting our own role provider but would like to do
as
little as possible.
Thanks
Tom
.
- Follow-Ups:
- Re: Role Providers Cache
- From: Tom
- Re: Role Providers Cache
- Prev by Date: Re: Newbie: How to ensure only domain admin could use an ASP.NET web page
- Next by Date: RE: Partial https in Firefox OK in IE6 - webresource.axt transmissions
- Previous by thread: Re: Extendig SqlMembershipprovider
- Next by thread: Re: Role Providers Cache
- Index(es):
Relevant Pages
|
|