[jira] [Resolved] (CXF-5641) WebSocket transport should support alternative bindings

["Colm O hEigeartaigh (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh resolved CXF-5641.
--------------------------------------
    Resolution: Won't Fix

> WebSocket transport should support alternative bindings
> -------------------------------------------------------
>
>                 Key: CXF-5641
>                 URL: https://issues.apache.org/jira/browse/CXF-5641
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>            Reporter: Sergey Beryozkin
>            Priority: Major
>
> The default WebSocket transport binding is better suited for JAX-RS endpoints where basically whatever the endpoint sends back is fine :-). Even when JAX-RS endpoints are used some alternative binding might need be used. And for WS endpoints it is not compatible with the 'soap' binding:
> http://msdn.microsoft.com/en-us/library/hh536812.aspx (link from Dan)
> Proposal: introduce the interface which will abstract away the details of how the data written to or read from the socket. If the WebSocket client provides no binding preferences as per WebSocket rules, then use the default binding, but if it does then try to find the binding which supports the client preference (how this extra bindings are discovered is to be discussed)
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)