Thanx Naing..
Yes this s the great way to share the knowledge... and i m learning a lot by this way.. i would like other to encourage and participate more.. this would also improve ur thinking process..
I have read some where on some JRun tutorial..
********************
Understanding the HttpSessionActivationListener
When sessions are activated or passivated, JRun notifies the HttpSessionActivationListener.
Passivation occurs when JRun does not invalidate a session, but backs it up to disk to free up resources, or when a "mirrored" JRun server fails and another JRun server picks up its sessions. This is also called session persistence.
Activation occurs when the client with a passivated session makes a request and the session must be retrieved from disk or loaded into a new JRun server.
The following example of a simple HttpSession event listener implements the methods of the HttpSessionActivationListener interface. When one of these events occurs, a line is printed to the standard output.
...
public void sessionWillPassivate(HttpSessionEvent event) {
System.out.println("Session was passivated");
}
public void sessionDidActivate(HttpSessionEvent event) {
System.out.println("Session was activated");
}
************************
So I think that sessions can be passivated in more then one way..
at least to free up the resources.. in addition to migration..
Naing wat do u say??
Any other idea from any one??
[ November 26, 2003: Message edited by: Andy Smith ]