Re: Some body Help

[Jeff Larsen]

There is NO way to know when a client kills their 
browser. HTTP is a stateless protocol. The only time
we know that the browser is alive is during a request.
After that, we don't know if the browser gets closed or
if the user just navigates elsewhere.

If you need to close down resources, just set your session
timeout appropriately and use the javax.servlet.http.HttpSessionBindingListener
interface to know when the session gets killed either by an
explicit user logout or a session timeout.

In any case, I would not recommend holding database connections
open for each session. Use a connection pool...

Jeff


- Original Message - 
From: "Uma Munugala" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 06, 2002 2:44 PM
Subject: Some body Help


> Hi  All
>  Iam using Tomcat 4.0 on NT.
> When a client kills a browser, I dont have any idea whether the client is
> alive or not from a servlet.
> when client is not alive I want release database connections and objects
> instances.
> how do I know which user is alive or which session is alive. Is there any
> software available.
> 
> Please help
> 
> 
> 
> Thanks
> Uma
> 
> 
> 
>  
> 
> 
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Some body Help

[Uma Munugala]

Hi  All
 Iam using Tomcat 4.0 on NT.
When a client kills a browser, I dont have any idea whether the client is
alive or not from a servlet.
when client is not alive I want release database connections and objects
instances.
how do I know which user is alive or which session is alive. Is there any
software available.

Please help



Thanks
Uma



 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: