tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: AsyncListener.onError and disconnected client
Date Thu, 25 Apr 2013 13:32:01 GMT
Mark Thomas wrote:
> On 25/04/2013 14:11, André Warnier wrote:
>> Sorry to butt in, but the issue interests me in another context.
>> My question : is there any kind of I/O operation that a servlet could do
>> to the response stream (even in-between two real "data" I/O) which would
>> be guaranteed to return an error if the client has closed the connection
>> in the meantime, no matter which Connector implementation underlies it ?
>> It would have to be something which does not really send any real data
>> byte, so as not to corrupt a response that may be partially under way. 
>> Some kind of "ping", to say it otherwise.
> With the current Servlet API, no.
> With direct access to the socket:
> BIO - no
> NIO - yes
> APR - don't know
Mmm. That's definitely not nice, is it ? It means that there is no real clean way for a 
Java webapp to do this and be portable.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message