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!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?
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().
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
