Hunsberger, Peter wrote:
To follow up with an old post about handling continuation ids as request parameters and how that could cause caching problems:
I wrote a quick set of changes to add the continuation id as a cookie in the setup method of one of my generators as follows:
...wait a minute!
Continuations cannot work with cookies or sessions. The continuations id is per individual page!
Or did I miss here something?
No, you've not. Usually, continuation is valid only for a particular page, and you can return to some other continuation. But I can imagine situation when flow is connected to some stateful app, where you can't go back to previous continuation. In such rare cases, it will make sense to have continuation in a cookie. But this is not helpful for generic app.
Vadim
