netty fires channelClosed() event when client only half close

[Huican Ping]

Hello Trustin,

We just noticed that when the client half closes the socket (such as when
write data is done, client close socket for write, but still want to read),
the netty always fires channelClosed() event.

Is there anyway to know whether it is a total close or half close?

The client sends data --> client half close (write done) --> client tries to
read the response back.


-- 
View this message in context: http://n2.nabble.com/netty-fires-channelClosed-event-when-client-only-half-close-tp3789745p3789745.html
Sent from the Netty User Group mailing list archive at Nabble.com.