For the other questions, see Igor's reply.
I've worked with WebObjects and therein a session is sent the awake() message before the request-response loop begins, and the sleep() message after the r-r loop finishes. I guess these inherited methods could include code to serialise the session, but I have never thought how they handle not serialising all the business objects (model) managed by the O/R framework. Maybe they don't serialise the session or pages but just keep them in memory. I believe Wicket does the serialisation, at least in part, to perhaps assist with clustering (processing requests on different servers etc).
Like Igor said, Wicket doesn't do that when there is no need. When there is - like when you work with session replication in clusters, it is the HttpSession implementation that does this. That is, *if* you use HttpSession as the storage. ISessionStore is a pluggable interface that handles any actual storage of the session objects. It's doesn't have a notify on the beginning/ ending of a request - I thought about it, but as the use cases and advantages/ disadvantages aren't clear yet, I didn't implement this... we *might* need that for client state saving though. For now, if you really need to do crazy stuff, you can always use a custom request cycle and session store, and let them work together. But you probably won't need it. Eelco ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
