[
https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862604#comment-13862604
]
Andriy Redko commented on CXF-5417:
-----------------------------------
Hi Sergey,
I've done a brief, preliminary investigation for this issue and possible
solutions.
Here are some very rough details (please correct me if I am wrong):
- there is no reliable way to detect that HTTP client disconnects (nor on
Jetty or Tomcat, ...)
- the workaround we may try is to intercept the exception on resume() and try
to understand if the disconnect took place
What do you think? Is it something we may try to implement or there is a better
solution I've missed?
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)
