cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Created] (CXF-5641) WebSocket transport should support alternative bindings
Date Mon, 24 Mar 2014 16:40:50 GMT
Sergey Beryozkin created CXF-5641:

             Summary: WebSocket transport should support alternative bindings
                 Key: CXF-5641
             Project: CXF
          Issue Type: Improvement
          Components: Transports
            Reporter: Sergey Beryozkin

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: (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

View raw message