>>> Palanisamy Easwaran <[EMAIL PROTECTED]> 10/21/99 10:54:49 AM >>>
> Is it possible to use this sort of API in
>all web servers without affecting
>their session implementation? (Do
>their servlet-engine allow me to do it?). I am
>very sure about the hitting issues due to this effort.
Servlet engines have access to the guts of the incomming request
before you do and work out the things that a servlet might want to
know, eg: is the request part of a session?
It is very difficult to replace this sort of behaviour without
re-writing the servlet engine.
You can get some way to making it seamless by overloading
HttpServletRequest but this will only help some of the way.
If you're happy to ignore the session management functionality inside
and totally replicate it in your servlets then you're ok, eg:
void service(HttpServletRequest req,HttpServletResponse resp)
{
String seshid=req.getParameter("mysessionid");
HttpSession sesh=MySessionManager.getSession(seshid);
if(sesh==null)
{ //no session
}
else
.....
}
We do this in Talk21 because our servlet engine did not support
sessions on paths (so we used ordinary parameters).
It's an awfull bind doing things like this.
If you want to write a distributed session implementation I'd be
happy to use your efforts to provide GNU-Paperclips with such code
(check out http://www.tapsellferrier.co.uk/gnupaperclips or mail me
privately for more info).
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
