Hi, I remember that the session objects are reside on the server-side and the client stores the sessionID, which is used to associate with any session-related information, in the in-memory cookie of the browser. Benny T
Actually, u create a Http Session object in the server, but in turn the Server send a Cookie to the Client with a small information about the Session such as session ID. Therefore every time user requests a page to view, the Cookie info goes along with the request and the Server reads the Cookie and identifies the current Session. If Cookie is disabled in your browser, Session will not work though it is created in the Server side. Regards JavaHunk
True, session rewriting will help. It may also be worth noting that session cookies are typically resident in memory only and disappear when the browser is closed, but they don't have to be "JavaHunk", we're light on rules here at the 'Ranch, but two that we quite strict about are our 'be nice' and naming policies. Unfortunately your display name is not valid. We require your display name to be two words: Your first name, a space then your last name. Fictitious names are not allowed. Please edit your profile so that you have a valid display name. Accounts with invalid display names get deleted thanks, Dave.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Where do Session objects live??? Server or Client??