[
https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865490#comment-13865490
]
Andriy Redko commented on CXF-5417:
-----------------------------------
Hi Sergey,
Quick follow up on previous comments. I have checked Jersey implementation and
by no surprise they do the same trick as we are discussing here. There are no
clear (if any at all) way to understand disconnect happens: server actually has
to write something to the socket and, if write fails, treat the error as
"client being disconnected".
What do you think?
Thanks.
Andriy
> Support optional JAX-RS 2.0 ConnectionCallback
> ----------------------------------------------
>
> Key: CXF-5417
> URL: https://issues.apache.org/jira/browse/CXF-5417
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS, Transports
> Reporter: Sergey Beryozkin
> Priority: Minor
>
> https://jax-rs-spec.java.net/nonav/2.0/apidocs/javax/ws/rs/container/ConnectionCallback.html
> lets JAX-RS 2.0 applications receive the notifications when a given client
> has disconnected.
> We can probably build something on top of the Jetty-specific connector and
> also enhance CXF Continuation API.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
