I'm looking for a reliable, relatively asynchronous way (at least on destroy) to handle the lifecycle of a single user's interaction with the application. The main purpose of this is to do some custom event logging.
In that light, I'm hoping for some additional information about Session scope:
1) Is the lifetime of a Session scoped bean tied directly to the server's regular parameters on session timeouts? In other words, is Seam destroying these Session beans at the same time the web server says the HttpSession has "expired"? Or does it use some other criteria?
2) I'm presuming @Destroy on a Session scoped bean is called in near proximity to when an HttpSession is expiring, and is typically asynchronous to any web requests... would that be a fair assumption?
2) yes (though it is synchronous with the web request if you call Seam.invalidateSession())