cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Schmitz, Jeffrey A" <Jeffrey.A.Schm...@boeing.com>
Subject RE: Flowscript Continuation ID parameter
Date Wed, 13 Jun 2007 20:45:01 GMT
On this subject, I'm thinking my scheme isn't going to work.  It looks
like it's the call to sendPageAndWait that generates a new
continuationID.  Since I'm using sendPageAndWait to invoke my
non-JXTemplateGenerator sitemap entry, I have no way to access the new
continuation ID from within my javascript before making the
sendPageAndWait call (since the ID doesn't yet exist), and after the
call it's too late since the new ID needs to be part of the input
parameter to the call.  It's a catch-22.  Is this right?  If so, what's
the solution?

Thanks,
Jeff

-----Original Message-----
From: Joerg Heinicke [mailto:joerg.heinicke@gmx.de] 
Sent: Wednesday, June 13, 2007 2:07 PM
To: users@cocoon.apache.org
Subject: Re: Flowscript Continuation ID parameter

On 12.06.2007 16:11, Askild Aaberg Olsen wrote:

>> Is there anything wrong with this approach (it seems to work)?  Is 
>> there a better way?
>>   
> I guess passing the continuation.id in the URI prevents caching in 
> your pipeline.

Actually you don't want to have that cached anyways since you need the
updated continuation id :)

Joerg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message