[
https://issues.apache.org/jira/browse/CXF-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982986#comment-13982986
]
Aki Yoshida commented on CXF-5715:
----------------------------------
Hi Sergey,
yes. we have some interesting part (bindings) to work on. :-)
for cxf's default binding, we need to add a Id-refId mechanism so that a
request-reply reliably works. Right now, we use no Id header, so we have FIFO.
for other standard bindings, I can work on the .net websocket binding. That
should not be complicated. I just don't know if this binding is really useful
(as it is not taking advantage of websocket), but from the interop point of
view, it may be interesting so that we can claim cxf interoperates with .net'
websocket ;-)
regards, aki
> Add a conduit part to WebSocket transport
> -----------------------------------------
>
> Key: CXF-5715
> URL: https://issues.apache.org/jira/browse/CXF-5715
> Project: CXF
> Issue Type: New Feature
> Components: Transports
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 3.0.0
>
>
> adding an AHC/Netty version of conduit to the websocket transport.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
