cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [Control flow] expire continuations code checked in!
Date Fri, 10 Jan 2003 15:23:54 GMT
Ovidiu Predescu wrote:
> 
> On Thursday, Jan 9, 2003, at 09:20 US/Pacific, Stefano Mazzocchi wrote:
> 
>> Ovidiu Predescu wrote:
>>
>>> Many thanks to Michael Melhem for his excellent work coming up with 
>>> the algorithm for expiring continuations and for implementing it! The 
>>> tests on my machine show the code works fine, so I checked it in CVS. 
>>> Thanks!
>>> I've also made some minor change to the control flow engine. When a 
>>> request is made for a continuation which has been expired or does not 
>>> exist, the JavaScript handleInvalidContinuation(kontId) is called. 
>>> This function is defined in system.js and by default it forwards the 
>>> request to a pipeline that matches "invalidContinuation.xml". This 
>>> should display an error page indicating the problem. If you want a 
>>> different pipeline to be invoked, just overwrite in your user scripts 
>>> the definition of handleInvalidContinuation().
>>
>>
>> shouldn't the error URI be unrelated to the .xml extensions? shouldn't 
>> it simply be "invalidContinuation" and then it's up to the sitemap to 
>> understand *what* type of content to send?
> 
> 
> You're right, the extension should not appear in the pipeline, I'll 
> remove it shortly.

Great. Thanks a lot, this new autoexpiring functionality is great.

-- 
Stefano Mazzocchi                               <stefano@apache.org>
--------------------------------------------------------------------



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


Mime
View raw message