Discussion Locked

Maintain client data with cookies

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This week's .NET e-newsletter describes how to maintain client data with cookies in ASP.NET. Do you use cookies to maintain client data? If not, what method do you use? What programming language do you use to maintain client data? Share your experiences in our discussion forum.

If you aren't subscribed to the .NET TechMail, visit our e-newsletter subcenter to subscribe to this free e-newsletter:
http://nl.com.com/MiniFormHandler?brand=builder&subs_channel=bldr_front_door&list_id=e605&;tag=fb

1 reply

by activemode

I normally will not use cookies when I develop an application, unless the client actually (specifically) requests it. From the time I started working with ASP.NET (after asp) so many years ago, I discovered that people are more likely to either lose the information in their computers through a crash or virus, or sometimes, they delete the information intentionally.

I would prefer to use "Sessions" that are Server Based or "Encripted Text Files" which even if they're read, cannot be deciphered.

Of course as long as you change your "UserID" for each login, you can always use QueryStrings.

I use "QueryStrings" for Desktop Websites, to save memory for the program and create a new UserID for each signin.

I use "Sessions" for Mobile Websites because of the different phone types that may not support cookies or QueryStrings.

This discussion is closed to new replies.