You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Akitoshi Yoshida (JIRA)" <ji...@apache.org> on 2015/03/19 16:48:39 UTC
[jira] [Commented] (CXF-6232) Refactor CXF's Atmosphere based
WebSocket transport for more flexible and extensible handling
[ https://issues.apache.org/jira/browse/CXF-6232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369580#comment-14369580 ]
Akitoshi Yoshida commented on CXF-6232:
---------------------------------------
I just noticed that I had incorrectly pushed the commits for CXF-6305 to this issue ticket.
The last commits for this ticket are for the other ticket.
> Refactor CXF's Atmosphere based WebSocket transport for more flexible and extensible handling
> ---------------------------------------------------------------------------------------------
>
> Key: CXF-6232
> URL: https://issues.apache.org/jira/browse/CXF-6232
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 3.0.2
> Reporter: Akitoshi Yoshida
> Assignee: Akitoshi Yoshida
> Fix For: 3.1.0, 3.0.5
>
>
> Currently, CXF's Atmosphere based WebSocket transport uses Atmosphere to handle WebSocket processing but uses its own message-level processing such as message format conversion.
> As Atmosphere provides its flexible framework to add such message format conversion and there are some custom extensions, it will be useful to use this feature in CXF's WebSocket transport.
> This will allow you to easily switch the message format or protocol or add a customized behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)