Yep, I agree with Johan on the points he gave. ISessionStore was created to abstract the actual storage of sessions, and the version we have now is finally something that works (we needed a few iterations to get it right). I'm using a custom session store for a project right now btw.
Like Johan said about pagemaps: they don't make sense in the context of client state saving. Pagemaps are very specific for supporting mulitple windows on the same session when session state cannot be rebuild from the client. Another thing about pagemaps is that I have grown less comfortable with the naming lately. It's a very generic term which doesn't communicate what it is used for. Furthermore, there's no conceptual extra; it's just a fix for a problem we had. If you think about it a bit more, what we actually have is a kind of sub sessions. The project I'm working on might actually have a good usecase where this special session scope might come in handy. With that app, users have to select a current context, which is then used for all subsequent requests until they switch to another context. The use case now is that a user should be able to open up another tab/ window, switch to a context, while the other window would stay in the same context. Currently, this is not elegantly possible. Having something like: Session Window(null) Window(auto-0) Window(named) would be used the same way as pagemaps, but is conceptually much stronger. A session would then be a composition of Windows (or whatever better name there might be... as a side note I don't like having INewBrowserWindowListener in package wicket too much as it points to something more specific then needs to be in that package); having always at least one, with no name (null, same as with page maps now). Such a window would work exactly the same as sessions work now, but are scoped on tab/ window instead. We'll need some more time to think about this, but something like I described above would be the way to go imo. Something for post 1.2 Eelco On 4/29/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
Just one to say one thing more for this MultiPageWindow support doesn't have much to do with back button support Those 2 are sperated issues. with multipage window support we are fixing things where the back button doesn't have to be touched at all. johan On 4/29/06, Michael Day <[EMAIL PROTECTED]> wrote: > I understand that we have a javascript/cookie solution, but I don't > like it. If I don't need back button support, why can't wicket deal > with multiple tabs/windows without javascript? Each time a page > containing a form is loaded, keep it in session as a separate object > - even if the page is there more than once. Then when the form is > submitted, make updates to the correct object (which was found by the > form action url). Surely I'm missing something? > > Michael Day > > On Apr 29, 2006, at 11:12 AM, Eelco Hillenius wrote: > > > But that's exactly what we have build in. It's not totally fail safe - > > clients need at least Javascript turned on but preferably also allow > > cookies - but given the technology it's the best we can do for server > > side store. > > > > Eelco > > > > > > On 4/29/06, Michael Day <[EMAIL PROTECTED]> wrote: > >> I don't want to test with two tabs, but the fact is that my users > >> will be doing it regardless of what wicket supports. The expired > >> page is logical to me also, but it is not acceptable. Using your > >> example below, can't we leave page 2 in memory? The form action is > >> set to a separate > >> "wicket interface", so can't the server somehow detect that this > >> request is *separate* from the requests happening on page 1? If not, > >> could an extra hidden form field help? > >> > >> Michael Day > >> > >> On Apr 29, 2006, at 6:30 AM, Johan Compagner wrote: > >> > >> > i will check out the deadlock. > >> > But can i say that when you disable multi window support you can > >> > start testing with 2 tabs > >> > or you really have to specify the pagemap youreself > >> > > >> > So if you have use/test 2 tabs and both are in the same pagemap > >> > multiwindow support MUST be on. > >> > Else it really won't work, that expired page doesn't really suprise > >> > me, that is pretty logical > >> > because we use a access stack. So if you load 1 then 2 then you > >> > submit 1 then 2 will be erased > >> > from memory on the serverside! > >> > > >> > johan > >> > > >> > > >> > > >> > > >> > On 4/28/06, Michael Day < [EMAIL PROTECTED]> wrote: Hi, > >> > > >> > There is an issue when automatic multi-window support is turned > >> off. > >> > > >> > I have a form on a bookmarkable page. I loaded it in two tabs, > >> then > >> > submitted both. This caused the second one to show an expired page > >> > error. When I click back and try to submit again, the connection > >> > stalls. > >> > > >> > Michael Day > >> > > >> > > >> > > >> > ------------------------------------------------------- > >> > 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&kid=120709&bid=263057&dat=121642 > >> > _______________________________________________ > >> > Wicket-user mailing list > >> > Wicket-user@lists.sourceforge.net > >> > https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > >> > >> > >> > >> ------------------------------------------------------- > >> 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&kid=120709&bid=263057&dat=121642 > >> _______________________________________________ > >> Wicket-user mailing list > >> Wicket-user@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wicket-user > >> > > > > > > ------------------------------------------------------- > > 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 > > Wicket-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > > ------------------------------------------------------- > 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?cmdlnk&kid0709&bid&3057&dat1642 > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user >
------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
