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] [Comment Edited] (CXF-5339) Introduce WebSocket CXF Transport
Date Thu, 27 Feb 2014 10:53:22 GMT

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

Sergey Beryozkin edited comment on CXF-5339 at 2/27/14 10:52 AM:
-----------------------------------------------------------------

Hi Aki, this is nice :-). 

What do we still have to sort out ?
I guess the whole configuration issue, specifically, how to enable it via the http-jetty schema
We thought we should strictly enforce POST for WS only but I wonder do we really need it,
given that HTTP accepts all verbs, and this is not a problem for CXF WS, so may be we should
not worry about it.

What kind of WebSocket binding does AsyncClient supports ? It clearly allows for all the HTTP
verbs and headers which is good. But what if we have say GWT client or some browser client
opening a WebSocket, can we hit the issue that this Web client will use the binding for passing
all HTTP verbs that we do not support in the Jetty transport ? I.e, we support the binding
that works with AsyncClient WebSocket, but this binding won't accept the frames sent by GWT/etc
client ?

Thanks, Sergey  


was (Author: sergey_beryozkin):
Hi Aki, this is nice :-). 

What do we still have to sort out ?
I guess the whole configuration issue, specifically, how to enable it via the http-jetty schema
We thought we should strictly enforce POST for WS only but I wonder do we really need it,
given that HTTP accepts all verbs, and this is not a problem for CXF WS, so may be we should
not worry about it.

What kind of WebSocket binding does AsyncClient supports ? It clearly allows for all the HTTP
verbs and headers which is good. But what if we have say GWT client or some browser client
opening a WebSocket, can we hit the issue that this Web client will use the binding for passing
all HTTP verbs that we do not support in the Jetty transport ? I.e, we support the binding
that works with AsyncClient WebSocket, but may not work with some other binding ?

Thanks, Sergey  

> Introduce WebSocket CXF Transport
> ---------------------------------
>
>                 Key: CXF-5339
>                 URL: https://issues.apache.org/jira/browse/CXF-5339
>             Project: CXF
>          Issue Type: New Feature
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Assignee: Aki Yoshida
>
> WebSocket transport will likely be supported on the server only. 
> It will allow users, specifically those not working directly with Camel, do Web-Socket
based Web UI targeting CXF endpoints returning some real time info.
> Additionally, hope is it will help revitalise LogBrowser project where having the log
or other events displayed for individual endpoints in real time can be quite cool; supporting
such a feature might help us basically move it into a sub-project   



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message