patches are always welcome. -igor
On Thu, Mar 11, 2010 at 1:23 PM, <martin.grot...@javakaffee.de> wrote: > From my basic understanding I'd say that for stateless pages nothing should > depend on the pageId. What do you think about incrementing the pageId when > it's first accessed? I'd like to create a patch for it to see if this works. > > Cheers, > Martin > > -- Urspr. Mitt. -- > Betreff: Re: Don't increment the Session.pageIdCounter for stateless pages? > Von: Igor Vaynberg <igor.vaynb...@gmail.com> > Datum: 10.03.2010 17:50 > > i think we can do this in 1.5 > > i would rather not mess with 1.4 because i think there is a lot of > code there that depends on the fact that the id is available right > away. > > please create a jira issue for this > > -igor > > On Mon, Mar 8, 2010 at 4:30 PM, Martin Grotzke > <martin.grot...@javakaffee.de> wrote: >> Hi, >> >> the Page.init(PageMap) invokes setNextAvailableId(), which invokes >> getSession().nextPageId() if isPageIdUniquePerSession is set. >> >> getSession().nextPageId() modifies the Session.pageIdCounter. >> >> When I have a session and afterwards access a stateless page, the >> Session.pageIdCounter is the only data that is changed in the session >> AFAICS, everything else is the same as in the request before. >> >> Is it possible _not_ to modify the Session.pageIdCounter if the page is >> really stateless (or just don't invoke Page.setNextAvailableId())? >> >> I'm interested in this, as I'm just implementing a feature for the >> memcached-session-manager ([1], memcached based session replication), >> which checks if session data has changed and replicates sessions only if >> this is provided. If session data did not change, the replication is >> omitted. Therefore, if the Session.pageIdCounter would be left unchanged >> for stateless pages, this would allow to make use of this feature in >> wicket apps. >> >> Thanx && cheers, >> Martin >> >> >> [1] http://code.google.com/p/memcached-session-manager/ >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
