[
https://issues.apache.org/jira/browse/CXF-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944933#comment-13944933
]
Sergey Beryozkin edited comment on CXF-5638 at 3/24/14 11:24 AM:
-----------------------------------------------------------------
The initial write over the web socket will include the metadata (status +
headers) + data [1].
This can complicate it a bit for JavaScript clients.
Proposal: if the JAX-RS method returns an OK response and it writes structured
events into StreamingOuput then it may make sense to optimize and not write the
metadata. This optimization can be enabled by the system or endpoint contextual
property.
To make this proposal working we should probably make a more compact
representation of the metadata such that the client can read it all in one line
and distinguish it from the other writes (though we can assume right now that
the write without a starting line break is a metadata write)
[1] https://cwiki.apache.org/confluence/display/CXF20DOC/WebSocket
was (Author: sergey_beryozkin):
The initial write over the web socket will include the metadata (status +
headers) + data [1].
This can complicate it a bit for JavaScript clients.
Proposal: if the JAX-RS method returns an OK response and it writes structured
events into StreamingOuput then it may make sense to optimize and not write the
metadata. This optimization can be enabled by the system or endpoint contextual
property.
[1] https://cwiki.apache.org/confluence/display/CXF20DOC/WebSocket
> Default WebSocket binding should optimize the metadata and optionally not
> write it
> ----------------------------------------------------------------------------------
>
> Key: CXF-5638
> URL: https://issues.apache.org/jira/browse/CXF-5638
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Sergey Beryozkin
> Priority: Minor
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
