Gregor J. Rothfuss wrote:
Andreas Hartmann wrote:
from what i understand, that is a global setting. might be good to
change that to sessions in general. what i don't like about
continuation id's in the request is that people bookmark a page and
then always get invalid continuation ids..
Sounds reasonable. Do you have experiences with adding the continuation
ID to the session?
i don't. it would be best to ask on the cocoon lists if anyone is doing
this.
Google revealed this:
"There are two options for sending the continuation id to the user's browser: It
can be embedded as a hidden field in the form that is sent back, or it can be
embedded in the URL to which the form will be posted. Needless to say,
encapsulating continuation ids within cookies is a bad idea, because a specific
cookie is common to all cloned instances of a browser window on a machine
whereas a continuation is specific to a particular instance of the browser
window only."
http://www-106.ibm.com/developerworks/library/j-contin.html
It looks like the request is the way to go when it comes to continuations.
Maybe BXE can be extended accordingly?
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
