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 <[EMAIL PROTECTED]>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
