Hi,
Thanks for all the answers! :-)
It's good to know the way the events should be treated and interpreted.
It's quite different from how it's described on
http://tomcat.apache.org/tomcat-6.0-doc/aio.html, and the JavaDoc does
not really describe the spec either.
Using the sendError method in the response and the new interpretation of
the events I think I will be able to manage.
One more question though: is there any way to do nonblocking output of
dynamic content (streams)? The above documentation only talks about
files on the file system.
Regards,
Sebastiaan
Rémy Maucherat wrote:
On 4/3/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
Hi,
Thanks again for the reply. I can't reproduce the END event so probably
I was mistaken, sorry about that. It is indeed the ERROR/TIMEOUT event.
If an exception occurs during the handling of this event (an unforseen
runtime exception for example), then tomcat calls the event method again
with the ERROR/TIMEOUT event, ad infinitum (or at least lots of times
;-))
Ok, it's the same for a read then (for which I could reproduce a
loop), as error/timeout is not really an error (it gives you the
opportunity to close end the request if you want to by calling
event.close).
Rémy
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
