Torsten Curdt [EMAIL PROTECTED] writes:
You basically have a tree of continuations on the server
side. You don't have to pop the stack to show a particular leave.
Right, I should have made it clearer, even for our case
where we don't
have a tree, I don't think this is worth
Ahh, I see what the issue is in general: there are currently no places
in our app where we've got anything other than a two state flow: GET -
POST jumping to another flow is a completely different GET/POST pair,
thus a new cookie and a new continuation. Two ways around this:
1) concatenate the
Torsten Curdt [EMAIL PROTECTED] writes:
Ahh, I see what the issue is in general: there are
currently no places
in our app where we've got anything other than a two state
flow: GET
- POST jumping to another flow is a completely different GET/POST
pair, thus a new cookie and a new
Hm... I cannot see how this would help. Continuations have
there stack on the server side.
In general you're right it's not useful, you'd only be able to support
this with a back button on the page that told the server to pop the
stack. You wouldn't have browser back button support.
I still
Torsten Curdt [EMAIL PROTECTED] writes:
Hm... I cannot see how this would help. Continuations have
there stack on the server side.
In general you're right it's not useful, you'd only be able
to support
this with a back button on the page that told the server to pop the
stack.
Torsten Curdt wrote:
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
Torsten Curdt [mailto:[EMAIL PROTECTED] asks:
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
Vadim Gritsenko [EMAIL PROTECTED] points out:
Torsten Curdt wrote:
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
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!
