2017-12-21 02:13:23 +00:00
|
|
|
/**************************************************************************/
|
|
|
|
/* emws_peer.h */
|
|
|
|
/**************************************************************************/
|
|
|
|
/* This file is part of: */
|
2017-12-21 02:47:16 +00:00
|
|
|
/* GODOT ENGINE */
|
|
|
|
/* https://godotengine.org */
|
2017-12-21 02:13:23 +00:00
|
|
|
/**************************************************************************/
|
2018-03-21 09:07:51 +00:00
|
|
|
/* Copyright (c) 2014-present Godot Engine contributors (see AUTHORS.md). */
|
|
|
|
/* Copyright (c) 2007-2014 Juan Linietsky, Ariel Manzur. */
|
2017-12-21 02:13:23 +00:00
|
|
|
/* */
|
|
|
|
/* Permission is hereby granted, free of charge, to any person obtaining */
|
|
|
|
/* a copy of this software and associated documentation files (the */
|
|
|
|
/* "Software"), to deal in the Software without restriction, including */
|
|
|
|
/* without limitation the rights to use, copy, modify, merge, publish, */
|
|
|
|
/* distribute, sublicense, and/or sell copies of the Software, and to */
|
|
|
|
/* permit persons to whom the Software is furnished to do so, subject to */
|
|
|
|
/* the following conditions: */
|
|
|
|
/* */
|
|
|
|
/* The above copyright notice and this permission notice shall be */
|
|
|
|
/* included in all copies or substantial portions of the Software. */
|
|
|
|
/* */
|
|
|
|
/* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, */
|
|
|
|
/* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF */
|
|
|
|
/* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. */
|
|
|
|
/* IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY */
|
|
|
|
/* CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, */
|
|
|
|
/* TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE */
|
|
|
|
/* SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. */
|
|
|
|
/**************************************************************************/
|
2019-01-01 11:46:36 +00:00
|
|
|
|
2022-07-23 21:41:51 +00:00
|
|
|
#ifndef EMWS_PEER_H
|
|
|
|
#define EMWS_PEER_H
|
2017-12-21 02:13:23 +00:00
|
|
|
|
2022-08-28 18:27:45 +00:00
|
|
|
#ifdef WEB_ENABLED
|
2017-12-21 02:13:23 +00:00
|
|
|
|
2023-06-13 14:56:21 +00:00
|
|
|
#include "packet_buffer.h"
|
|
|
|
#include "websocket_peer.h"
|
|
|
|
|
2020-11-07 22:33:38 +00:00
|
|
|
#include "core/error/error_list.h"
|
2017-12-21 02:13:23 +00:00
|
|
|
#include "core/io/packet_peer.h"
|
2020-11-07 22:33:38 +00:00
|
|
|
#include "core/templates/ring_buffer.h"
|
2023-06-13 14:56:21 +00:00
|
|
|
|
|
|
|
#include <emscripten.h>
|
2017-12-21 02:13:23 +00:00
|
|
|
|
2020-10-23 16:33:20 +00:00
|
|
|
extern "C" {
|
|
|
|
typedef void (*WSOnOpen)(void *p_ref, char *p_protocol);
|
|
|
|
typedef void (*WSOnMessage)(void *p_ref, const uint8_t *p_buf, int p_buf_len, int p_is_string);
|
|
|
|
typedef void (*WSOnClose)(void *p_ref, int p_code, const char *p_reason, int p_is_clean);
|
|
|
|
typedef void (*WSOnError)(void *p_ref);
|
|
|
|
|
|
|
|
extern int godot_js_websocket_create(void *p_ref, const char *p_url, const char *p_proto, WSOnOpen p_on_open, WSOnMessage p_on_message, WSOnError p_on_error, WSOnClose p_on_close);
|
|
|
|
extern int godot_js_websocket_send(int p_id, const uint8_t *p_buf, int p_buf_len, int p_raw);
|
2021-07-29 20:11:27 +00:00
|
|
|
extern int godot_js_websocket_buffered_amount(int p_id);
|
2020-10-23 16:33:20 +00:00
|
|
|
extern void godot_js_websocket_close(int p_id, int p_code, const char *p_reason);
|
|
|
|
extern void godot_js_websocket_destroy(int p_id);
|
|
|
|
}
|
|
|
|
|
2017-12-21 02:13:23 +00:00
|
|
|
class EMWSPeer : public WebSocketPeer {
|
|
|
|
private:
|
2021-02-08 09:57:18 +00:00
|
|
|
int peer_sock = -1;
|
2017-12-21 02:13:23 +00:00
|
|
|
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
State ready_state = STATE_CLOSED;
|
|
|
|
Vector<uint8_t> packet_buffer;
|
|
|
|
PacketBuffer<uint8_t> in_buffer;
|
|
|
|
uint8_t was_string = 0;
|
|
|
|
int close_code = -1;
|
|
|
|
String close_reason;
|
|
|
|
String selected_protocol;
|
|
|
|
String requested_url;
|
|
|
|
|
2024-04-22 14:34:44 +00:00
|
|
|
static WebSocketPeer *_create(bool p_notify_postinitialize) { return static_cast<WebSocketPeer *>(ClassDB::creator<EMWSPeer>(p_notify_postinitialize)); }
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
static void _esws_on_connect(void *obj, char *proto);
|
|
|
|
static void _esws_on_message(void *obj, const uint8_t *p_data, int p_data_size, int p_is_string);
|
|
|
|
static void _esws_on_error(void *obj);
|
|
|
|
static void _esws_on_close(void *obj, int code, const char *reason, int was_clean);
|
|
|
|
|
|
|
|
void _clear();
|
|
|
|
Error _send(const uint8_t *p_buffer, int p_buffer_size, bool p_binary);
|
2017-12-21 02:13:23 +00:00
|
|
|
|
|
|
|
public:
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
static void initialize() { WebSocketPeer::_create = EMWSPeer::_create; }
|
|
|
|
|
|
|
|
// PacketPeer
|
2022-04-05 10:40:26 +00:00
|
|
|
virtual int get_available_packet_count() const override;
|
|
|
|
virtual Error get_packet(const uint8_t **r_buffer, int &r_buffer_size) override;
|
|
|
|
virtual Error put_packet(const uint8_t *p_buffer, int p_buffer_size) override;
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
virtual int get_max_packet_size() const override { return packet_buffer.size(); }
|
2017-12-21 02:13:23 +00:00
|
|
|
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
// WebSocketPeer
|
|
|
|
virtual Error send(const uint8_t *p_buffer, int p_buffer_size, WriteMode p_mode) override;
|
2023-01-20 00:51:35 +00:00
|
|
|
virtual Error connect_to_url(const String &p_url, Ref<TLSOptions> p_tls_client_options) override;
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
virtual Error accept_stream(Ref<StreamPeer> p_stream) override;
|
2022-04-05 10:40:26 +00:00
|
|
|
virtual void close(int p_code = 1000, String p_reason = "") override;
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
virtual void poll() override;
|
|
|
|
|
|
|
|
virtual State get_ready_state() const override;
|
|
|
|
virtual int get_close_code() const override;
|
|
|
|
virtual String get_close_reason() const override;
|
|
|
|
virtual int get_current_outbound_buffered_amount() const override;
|
|
|
|
|
2022-04-05 10:40:26 +00:00
|
|
|
virtual IPAddress get_connected_host() const override;
|
|
|
|
virtual uint16_t get_connected_port() const override;
|
[WebSocket] Refactor websocket module.
This commit is a huge refactor of the websocket module.
The module is really old, and some design choices had to be
re-evaluated.
The WebSocketClient and WebSocketServer classes are now gone, and
WebSocketPeer can act as either client or server.
The WebSocketMultiplayerPeer class is no longer abstract, and implements
the Multiplayer API on top of the lower level WebSocketPeer.
WebSocketPeer is now a "raw" peer, like StreamPeerTCP and StreamPeerTLS,
so it emits no signal, and just needs polling to update its internal
state.
To use it as a client, simply call WebSocketPeer.coonect_to_url, then
frequently poll the peer until STATE_OPEN is reached and then you can
write or read from it, or STATE_CLOSED and then you can check the
disconnect code and reason).
To implement a server instead, a TCPServer must be created, and the
accepted connections needs to be provided to
WebSocketPeer.accept_stream (which will perform the HTTP handshake).
A full example of a WebSocketServer using TLS will be provided in the
demo repository.
2022-09-24 20:44:44 +00:00
|
|
|
virtual String get_selected_protocol() const override;
|
|
|
|
virtual String get_requested_url() const override;
|
2017-12-21 02:13:23 +00:00
|
|
|
|
2022-04-05 10:40:26 +00:00
|
|
|
virtual bool was_string_packet() const override;
|
|
|
|
virtual void set_no_delay(bool p_enabled) override;
|
2017-12-21 02:13:23 +00:00
|
|
|
|
|
|
|
EMWSPeer();
|
|
|
|
~EMWSPeer();
|
|
|
|
};
|
|
|
|
|
2022-08-28 18:27:45 +00:00
|
|
|
#endif // WEB_ENABLED
|
2017-12-21 02:13:23 +00:00
|
|
|
|
2022-07-23 21:41:51 +00:00
|
|
|
#endif // EMWS_PEER_H
|