On 24.5.2005 22:40 Uhr, Andreas Hartmann wrote: > 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?
How do you give the new continuation id back to BXE? (or any other editor, for that matter). I think, it would possible without too much hassle to be implemented in BXE, but lenya would need its own TransportDriver, AFAICS (which is not a big task per se, just additional maintenance work). Kupu will have the same problem. An unified approach there (how such things as "we now have a new Save URL" should be handled, resp. communicated) would maybe help all of us ;) chregu -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | [EMAIL PROTECTED] | gnupg-keyid 0x5CE1DECB --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
