[WICKET-2782] Don't increment the Session.pageIdCounter for stateless pages

• Type: Improvement
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4.7
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Grotzke
• Created: 13/Mar/10 21:33
• Updated: 28/Jan/14 10:07

Description

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, 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/

PS: this has already been posted on the mailing list:
http://old.nabble.com/Don%27t-increment-the-Session.pageIdCounter-for-stateless-pages--tp27829803p27829803.html

Issue Links

• relates to: WICKET-5473 Wicket does not handle non in-memory Httpsessions correctly