Defold-WebSocket (DEPRECATED)

Link · May 28, 2019, 6:10pm

How to do it? I’m new. I thought that I installed the extension and use it

Please add the githab guide to the readme. It is useful to many, since without crutches in any way.

britzl · May 28, 2019, 7:41pm

Here you go: GitHub - britzl/defold-websocket: DEPRECATED - Use https://github.com/defold/extension-websocket instead! · GitHub

Link · May 28, 2019, 8:00pm

Thanks! Works!

Link · June 12, 2019, 4:52pm

Hello!
Does not work on the android (USB modem and wi-fi too)

MacOS Mojave 10.14.5
Android 9.0 (Asus Zenfone M1)

britzl · June 12, 2019, 6:31pm

How are you testing on mobile? I’m guessing that you’ve downloaded dmengine.apk, installed that and target it? This won’t work. The Defold-Websocket library uses a native extension, meaning that it contains native code that needs to be compiled into a custom engine for you. You must bundle a debug version and install it and target that version while you iterate on your game.

Link · June 12, 2019, 9:47pm

wow… where can I read about it?

Link · June 12, 2019, 9:50pm

I have now tried your code on html5 - it does not work (

britzl · June 13, 2019, 3:42am

Where can you read about what? How to bundle for mobile?

britzl · June 13, 2019, 3:44am

This is mentioned here: defold-websocket/README.md at master · britzl/defold-websocket · GitHub

If you try on a websocket server of your own or something like Colyseus it will work as expected.

Link · June 13, 2019, 8:44am

I use websockets in about 10 html5 projects, including Corona SDK (html5). Problems with Sec-WebSocket-Protocol never existed.

Crash even when using my server, for example wss://words.webday.ru/wsm

How can I prevent the transfer of the protocol in html if I do not want to specify it? This is an optional parameter. If I use any protocol, but in html5 the value is still “binary”

By the way, for some reason, in the example, instead of the protocol, you specify: ws / wss

Headers:
From HTML5

From defold simulator (macos)

On the server I use the most popular solution for nodejs: https://www.npmjs.com/package/ws
There have never been any problems

britzl · June 13, 2019, 9:26am

Let me take a look at this again and see if anything can be done.

Yes, that’s how it is supposed to work:

github.com/britzl/defold-websocket

websocket/sync.lua

master


      
              reason = err
            end
            self:sock_close()
            if self.on_close then
              self:on_close()
            end
            self.state = 'CLOSED'
            return was_clean,code,reason or ''
          end
          
          local connect = function(self,ws_url,ws_protocol,ssl_params)
            if self.state ~= 'CLOSED' then
              return nil,'wrong state',nil
            end
            local protocol,host,port,uri = tools.parse_url(ws_url)
            -- Preconnect (for SSL if needed)
            local _,err = self:sock_connect(host,port)
            if err then
              return nil,err,nil
            end
            if protocol == 'wss' then

Link · June 13, 2019, 9:43am

But then there is confusion. Through the simulator headers = ws / wss / nil.
And through html always = binary

britzl · June 13, 2019, 9:53am

Yes, I understand the confusion. This is how it works:

On desktop and mobile we have socket connections using LuaSocket built into the engine. In order to support the WebSocket protocol we need functionality to upgrade the socket connection to a WebSocket connection. This is done by lua-websocket on which defold-websocket is based. So basically all of the Lua code in the project comes from lua-websocket and it is there to support WebSocket connections on desktop and mobile.
On HTML5 however there is no such thing as a socket. You can make HTTP requests and you can create WebSockets. When you create a TCP socket connection in an HTML5 build it will automatically be upgraded to a WebSocket. This is done by Emscripten (and Websockify). And that is why you find two different code-paths throughout the client_async.lua file. And it is the Emscripten WebSocket connection that sets the Sec-Websocket-Protocol to “binary”.
- We can maybe fix this by building using some other compiler flags or build parameters but I’m not sure about this.

filazopovich · June 14, 2019, 12:05pm

Hello!
What about support of arm64-android platform for this extension? There are problem with defold-luasec dependency.

Mathias_Westerdahl · June 14, 2019, 1:06pm

This is about another extension (defold-luasec), perhaps it’s possible to enable issues on that fork, @britzl?

Link · June 14, 2019, 4:31pm

I checked my server returns in the headers “binary” too. But crash happens anyway

even has time to accept the message, but breaks off

That is, with a handshake, everything is fine! But when receiving a message = crash

britzl · June 14, 2019, 6:17pm

I’ve released a new version of luasec with openssl compiled for arm-64: Release Defold-LuaSec 1.1.0 · britzl/defold-luasec · GitHub

britzl · June 14, 2019, 6:18pm

Strange. @selimanac and @endel have you been able to connect from an HTML5 Defold client to a Colyseus server?

selimanac · June 14, 2019, 7:04pm

I just build tic-tac example as html5 and test it on my local environment. Seems like it is working. To be honest, I didn’t understand the problem here.

Link · June 15, 2019, 6:13pm

The Colosseum transmits binary data. That is why it works. And I pass in all my projects = string (json), like most of the developers who use web sockets.

Is it possible to somehow choose other data types? Web socket capabilities are limited in this view.

my: