decoding messages from express + socket.io under node about protobuf.js HOT 7 CLOSED

Correct me if I am wrong, but as far as I am concerned socket.io does not yet handle binary data well as binary support on e.g. websockets is a rather new feature. There are add-ons like Delivery.js which might use base64 encoding. This isn't optimal but should probably work.

Your best bet, however, is to use WebSockets with binaryType="arraybuffer": https://developer.mozilla.org/en-US/docs/Web/API/WebSocket

from protobuf.js.

yeah, I thought as much - so I tried ws.io but alas, same problem. I guess it does not really matter, I may just pipe a binary prepared file for the test. or Kaazing or something.

from protobuf.js.

Actually you do not need any middleware at all. Just use WebSocket in the browser and ws on node.

http://www.w3.org/TR/websockets/
https://github.com/einaros/ws

from protobuf.js.

Sweet, thanks. Will look later, still working on a extend API through the parser and builder.prototype.import

from protobuf.js.

seems a little better - except for sending the foo.toArrayBuffer() arrives on the client with just the correct byteLength but not the data (according to Charles / Wireshark and WebInspector). sigh...

from protobuf.js.

Hard to tell what's happening there. I guess it's a problem with ws/binaryType or similar (probably not protobuf). If you are going to investigate this further, let me know :)

from protobuf.js.

it fails to coerce data, ByteBuffer refuses to wrap anything passed to it.
except for an instance of ArrayBuffer and then gets byteLength but does not
decode... bit stumped.

On Sunday, June 2, 2013, dcode wrote:

Hard to tell what's happening there. If you are going to investigate this
further, let me know :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/30#issuecomment-18806181
.

Dimitar Christoff

"JavaScript is to JAVA what hamster is to ham"
@D_mitar - https://github.com/DimitarChristoff

from protobuf.js.