[
https://issues.apache.org/jira/browse/WICKET-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2782.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Assignee: Igor Vaynberg
> Don't increment the Session.pageIdCounter for stateless pages
> -------------------------------------------------------------
>
> Key: WICKET-2782
> URL: https://issues.apache.org/jira/browse/WICKET-2782
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.7
> Reporter: Martin Grotzke
> Assignee: Igor Vaynberg
> Fix For: 1.5.0
>
>
> 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
