cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5417) Support optional JAX-RS 2.0 ConnectionCallback
Date Tue, 07 Jan 2014 11:39:50 GMT

    [ https://issues.apache.org/jira/browse/CXF-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864129#comment-13864129
] 

Sergey Beryozkin commented on CXF-5417:
---------------------------------------

Hi Andriy,

I think the idea behind JAX-RS ConnectionCallback is to help with optimizing the async applications,
example, they can clean up the current AsyncResponse state, and I think CXF itself will be
able to optimize a bit. This is why it is optional to support but can be helpful, I would
not be surprised if RI were supporting it. Some users asked about it too.   
Does Jetty offer a handler which can callback if it detects the disconnect ? If yes, then
we can offer a link to it and document that it is not guaranteed to be predictable, etc.
Let us know please if you find Jetty offering a handler, we can then discuss how to link to
it
Thanks, Happy New Year
Sergey

> 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)

Mime
View raw message