Just to make a minor clarification, .NET has the ability to store session data in a database but it can also store it in memory (both in-process and out-of-process).
Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffry Houser Sent: Monday, November 19, 2007 1:51 PM To: [email protected] Subject: Re: [flexcomponents] Session variables In the ColdFusion world, session variables are used to get around the stateless of a browser. Cookies are passed back and forth between each page request, which the server ties into "in memory" variables. From what I understand, in the .NET world the concept is very similar, except that .NET stores session variables in a database, not in memory. ( I could be completely wrong ). In a Flex application, you aren't performing multiple page requests in the same vein that you would when serving dynamically generated HTML, and therefore don't need session variables. Store your "session" state as part of the Flex application, not on the remote server.
