Session state is not sent to the client and is in fact stored in server memory. I think what you want to refer to is actually called ViewState.
On May 24, 9:45 pm, Davej <[email protected]> wrote: > Ok, I'm an ASP.NET noob and I'm reviewing some basics... > > What are the best guidelines for using Session State? The concept of > sending encoded data out to the user just so the data can be sent back > seems a bit crazy to me. Wouldn't it be better if session data was > just stored in memory with some sort of expiration scheme? If the data > is sent out (added to the session) is it really 100% secure? Thanks. -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
