You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. When I'm doing development tests I use http and ws protocols, but when deploying to production I have the need to connect to the server using https and wss. Maybe the best solution would be to separate into two URIs, one for the API and one for the GameServer.
I am available to send a PR.
tks.
The text was updated successfully, but these errors were encountered:
I think we could come up with an API for all clients in the next version. Something like:
new Client({ host: "some-endpoint.com", port: 2567, secure: false })
new Client("ws://some-endpoint.com:2567", { secure: false })
I'm considering JavaScript for these API's, ideally we should come up with something that is easily ported to other languages without having too many custom data structures.
endel
changed the title
Allow set protocol
Allow to specify the protocol (SSL)
Oct 20, 2020
Hi. When I'm doing development tests I use http and ws protocols, but when deploying to production I have the need to connect to the server using https and wss. Maybe the best solution would be to separate into two URIs, one for the API and one for the GameServer.
I am available to send a PR.
tks.
The text was updated successfully, but these errors were encountered: