J
James Geurts
This is probably more of an ASP.Net situation rather than
c#, but since all of my code behind is in c#, maybe it
fits here. I'm wondering, generally, at what point is it
too inefficient to store information in a client cookie
rather than retrieve it from a datastore.
Now, I see the advantage of not storing it in a cookie,
but a lot of programs already use cookies to store things
from user credentials (roles) to specific user settings.
Now I know that part of the dilemma is how much data
needs to be stored/retrieved. So I would like to know in
general situations. A better question would probably
be "How do you determine where to store information for
the current user/session?" The options as I see it:
System cache
Datastore (SQL, Access, Xml)
User cookie
I would just think that storing information in a cookie
would actually take longer to retrieve and process than
just making a request to a datastore. Any opinions
welcome?
c#, but since all of my code behind is in c#, maybe it
fits here. I'm wondering, generally, at what point is it
too inefficient to store information in a client cookie
rather than retrieve it from a datastore.
Now, I see the advantage of not storing it in a cookie,
but a lot of programs already use cookies to store things
from user credentials (roles) to specific user settings.
Now I know that part of the dilemma is how much data
needs to be stored/retrieved. So I would like to know in
general situations. A better question would probably
be "How do you determine where to store information for
the current user/session?" The options as I see it:
System cache
Datastore (SQL, Access, Xml)
User cookie
I would just think that storing information in a cookie
would actually take longer to retrieve and process than
just making a request to a datastore. Any opinions
welcome?