Hi all, I'm currently debugging some code to look for httpsession storage issues and i may have overlooked something but it seems to me that specific page state, that is session variables that only belong to a single page, are always returned in the session object even if that page is not called/used from the client ?
This seems to me like there can be some optimization to the httpsession storage where only those session objects are returned for the requested page and not all of them. for example: I'm requesting a page /package/index and i see that the session also contains page state for the other pages: state:Login:<somevalue> state:Welcome:<somevalue> state:Index:<myvalue> I'm only interested in <myvalue>, the other values belong to other pages.. Is this something that can be optimized or did i miss crucial parts ? Thx -- View this message in context: http://tapestry.1045711.n5.nabble.com/HttpSession-state-storage-tp5716273.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
