-
Notifications
You must be signed in to change notification settings - Fork 59
Protobuf support #21
Comments
It does not use protobuf, but you can use protobuf above it. This client is quite low-level, so I do support only what the STOMP spec support. |
I can see from the source that everything is converted into string.
If the data is converted into string I cannot deserialize it then using protobuf js. |
Going through |
what about going through string for headers and leave the body intact for further processing by the protobuf library? |
Could you show me how you would do that? A clean PR (pull request) could help. |
Have a look at the following: |
This is not XHR protocol with HTTP, it's websocket with STOMP frames. |
It is still read as string. So corruption happens when original body contect is read as string. |
I have seen the same problem and suggestion I wrote here in this thread but it seems that it is not maintained anymore |
This is fixed in this fork |
adamish commented on Dec 10, 2014 comment is fixed here? |
?? |
I can confirm that this was not fixed as you stated. |
Spring 5.0.7+ recommends this variant of the STOMP library for browser clients, and while it's possible to send binary via this library (and the Spring implementation of STOMP is binary safe), this issue prevents developers from sending binary replies. So without some massaging on the server, protobuf is not supported. That said, I'm not sure if this library is still the best fork for developers to use. |
This fork matches my need, but you are welcome to contribute via PR ;) |
Is this library compatible with protobuf?
Thanks.
The text was updated successfully, but these errors were encountered: