Hi,
I'm sorry. It's my misunderstand. Nic's example is alright. But I didn't clearly understand in that example yet. Did it leave implementation detail to implementers ?? ... If so ... then I have to make a class that manage session (maybe MySessionManager) and then to create session table or something to share between many request , Right ??
Thank you,
Siros
-----Original Message-----
From: Nic Ferrier [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, October 21, 1999 7:54 PM
To: [EMAIL PROTECTED]
Subject: Re: Own Session Management API
I think you've got the wrong end of the stick Siros.
The method I was using was from a purely conceptual class called
MySessionManager which replaces the session management behaviour of
the servlet engine.
This is what the original post was about, whether such a thing was
possible to do.
You're partly right though. Even though the sesison manager is
outside the servlet engine one should probably still try to make it
look standard by providing a getSession(String,boolean) method rather
than the plain old getSession(String).
Note though that any class like my MySessionManager has no interface
in the Servlet API. It must return valiid HttpSession objects but it
is not itself an API entity., so how it actually chooses to do it is a
decision for only the implementor.
Nic Ferrier
