cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Philippe CLEMENT (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7007) Allow customizing atmosphere's config parameters when using websocket transport
Date Fri, 12 Aug 2016 09:45:20 GMT

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

Jean-Philippe CLEMENT commented on CXF-7007:
--------------------------------------------

If the client WebSocket sends the binaryType in the request (header?) then it might dynamically
be used in CXF, rather than a static server configuration.
If the binaryType is not sent by the browser WebSocket then that option could be sent as extra
request header in the request. For instance:
        ws://host:port/cxf/some/sample/r/norg.atmosphere.websocket.binaryWrite=true
or
        ws://host:port/cxf/some/sample/r/nmode=binary
or - if that makes sense
        ws://host:port/cxf/some/sample/r/nmode=blob
        ws://host:port/cxf/some/sample/r/nmode=arraybuffer

> Allow customizing atmosphere's config parameters when using websocket transport
> -------------------------------------------------------------------------------
>
>                 Key: CXF-7007
>                 URL: https://issues.apache.org/jira/browse/CXF-7007
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Akitoshi Yoshida
>
> The atmosphere framework in CXF is currently set up with some predefined options and
there is no way to change this setting except customizing its protocol interceptor. To be
able to customize the behavior of websocket processing, those options to be made configurable,
possibly using a specific Feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message