Why is this only specific to sessions?

[Abimaran Kugathasan]

We know, that, objects can be bounded to session, request, and application. (leave the page for JSP), Why is it specific to session bounded objects to get notification, when they about to be added and removed to session (HttpSessionBindingListener)? There is HttpSessionActivationListener interface, to get notification when the session about to be migrate. But, why is this special to session? No other scopes(request, application) have this feature?

Thanks!

[Sudhakar Duraiswamy]

Well its the need that is the basis for features added.

My Logical inner voice says , that since its the session thats responsible for maintaining the state and available in memory for access (unlike request which gets destroyed immediately once its purpose is served), and available in thousands in server's memory (unlike servletcontext only one available for the entire application) one would need all the trackings that one can think of to efficiently maintain (adding /removing/updating/invalidating)session objects ensuring that the application is always performant

[Abimaran Kugathasan]

Any reasons?

[Ankit Garg]

Do you see any real life use of a HttpRequestBindingListener or ServletContextBindingListener??