We are developing a high load application. One of our requirements is to have no server side sessions.
As the documentation says, Tapestry tries it's best to not start a HttpSession until it has to. But I need a tighter guarantee, that it does not start a HttpSession ever. For example I would prefer Tapestry to throw an error if any components declare a property persistent, or ever tries to create a session, so that we can replace that component. Any ideas on how I can accomplish this? Does there happen to be a service whose job is to create sessions, that I could replace with HiveMind? I just figured out one way; as I was writing this. Use a Webapp Filter to replace the HttpServletRequest object with one that reimplements the getSession methods to throw an exception. This will force the guarantee of no serverside sessions. But the question still remains, how will Tapestry react. Could Tapestry work under such a strict environment, etc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
