0

Do we have a spec standard for designing a session manager? IMO, these are what a session should process:

  1. a unique id for each session should be assigned (session id);
  2. should be able to maintain attributes in the form of pairs;
  3. should be able to check the client's availability (for instance, the client exits);
  4. should be able to destroy a session;
  5. anything more?

Do we have some good example of a session manager?

Vadim Kotov
  • 8,084
  • 8
  • 48
  • 62
J.E.Y
  • 1,173
  • 2
  • 15
  • 37
  • 1
    Since you tagged the question `httpsession`, I wonder what application you're developing. Are you developing a JSP/Servlet application? If so, why don't you just utilize the Servlet API provided `HttpSession` object? It does already all that work. It's been specified in Servlet API specification and it's fully transparently managed by the servletcontainer (Tomcat, Glassfish, JBoss AS, etc). – BalusC Jul 01 '11 at 12:17
  • thanks for response. No, this is not a webapp, the clients are standalong C# apps, I wanted to maintain a conversation with them when they log in, until they log out or time out. My guess is that demand for such a httpsession-like solution should be common, if not, I have to build my own. – J.E.Y Jul 02 '11 at 13:07
  • OK, I removed the irrelevant tag. – BalusC Jul 02 '11 at 19:28

0 Answers0