[
https://issues.apache.org/jira/browse/QPIDJMS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042761#comment-16042761
]
Robbie Gemmell commented on QPIDJMS-293:
----------------------------------------
I think any change on the sending side would be a new JIRA, but to address the
comment..
At the moment, the client will emit a single WebSocket message/frame containing
all the current bytes provided from proton at a given point, which given
peculiarities of how proton-j works I beleive will be up to the clients (not
brokers) AMQP max frame size and containing up to 2 transfer frames for an AMQP
message. The client has no way to separate AMQP tranfers into particular
WebSocket frames because it only sees the bytes. The best it could currently do
would be to arbitrarily split bytes into multiple WebSocket messages/frames
(wouldnt really matter which). Other than the mentioned peculiarties, there is
no correlation between the emitted AMQP frames and the bytes in the Websocket
message/frames and their respective sizes currently.
> the WebSocket transport does not handle continuation frames
> -----------------------------------------------------------
>
> Key: QPIDJMS-293
> URL: https://issues.apache.org/jira/browse/QPIDJMS-293
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.23.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.24.0
>
>
> the WebSocket transport does not handle continuation frames, only the primary
> Binary frames, it needs to handle both. Indentified from investigation of
> followup comments on QPIDJMS-290 once 0.23.0 was under vote.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
