Defold-WebSocket (DEPRECATED)

[Link]

Pleaaaaaase, add select type

[fyrros]

I have exact same issue! Any way to fix it?

[Link]

No

[britzl]

Remind me again. What is the problem here? What do you mean by “type” in the context of a WebSocket?

[Link]

Websockets can take two types, but in this implementation you can send/put only binary data.

In android / ios / simulator - two types
in hmtl5 - only binary!

Really needed: STRING!

[britzl]

Websockets can take two types

Can you provide some documentation? Is this the Sec-WebSocket-Protocol header?

In android / ios / simulator - two types
in hmtl5 - only binary!

In my example provided with defold-websocket I passed the wrong data to ws_protocol. I took a look at the code yesterday and made a minor change to handle this properly:

britzl/defold-websocket/blob/master/examples/websocket.gui_script#L89-L95

With this change all but the HTML5 platform allows you to define whatever value to Sec-WebSocket-Protocol in the second argument to self.ws:connect(url, [ws_protocol], [sslparams]).

In HTML5 builds the whole websocket setup is done by Emscripten in which case the Sec-WebSocket-Protocol is always binary. I have an idea to not use Emscripten and sockets and instead immediately use JavaScript to create the websocket.

Really needed: STRING!

The thing I do not understand still is why? I’m thinking that with the type set to binary you would be able to pass any kind of data. Strings are after all bytes right?

[Link]

I thought so too, but it’s not. Socket breaks

Defold-WebSocket

I checked my server returns in the headers “binary” too. But crash happens anyway [29] even has time to accept the message, but breaks off [02] [04] That is, with a handshake, everything is fine! But when receiving a message = crash

[Link]

I have an idea to not use Emscripten and sockets and instead immediately use JavaScript to create the websocket.

It’s cool idea!
I worked with sockets on corona sdk in html including. It was done on pure JS

[britzl]

I thought so too, but it’s not. Socket breaks

Is there a chance for me to play around and try to connect against a server where there’s a crash when sending and receiving data?

[Link]

Made for the test. Send any text and it returns in a second

wss://lost.webday.ru/britzl_test99

[Link]

I think here you can also test
http://websocket.org/echo.html

ws://demos.kaazing.com/echo – Binary
ws://echo.websocket.org – String

They also talk about the fact that there is a difference in data types.

[endel]

I have an idea to not use Emscripten and sockets and instead immediately use JavaScript to create the websocket.

Not using emscripten for the HTML5 builds would be really good indeed. I’ve had some headaches by parsing multiple binary messages being delivered in a single “on_message” callback from the HTML5 builds a while back (it doesn’t happen on Desktop builds). Fortunately I’ve managed to work around that, but my workaround is a bit fragile.

[Link]

Excuse me! Have you added two data types for HTML5? I would like to return to development

[britzl]

Please note that this extension is deprecated in favour of the new native WebSocket extension: Extension-websocket

I believe Colyseus and others have migrated to the new one.

Locking this topic.