2017-12-21 03:13:23 +01:00
|
|
|
/**************************************************************************/
|
|
|
|
/* websocket_peer.h */
|
|
|
|
/**************************************************************************/
|
|
|
|
/* This file is part of: */
|
2017-12-21 03:47:16 +01:00
|
|
|
/* GODOT ENGINE */
|
|
|
|
/* https://godotengine.org */
|
2017-12-21 03:13:23 +01:00
|
|
|
/**************************************************************************/
|
2018-03-21 10:07:51 +01:00
|
|
|
/* Copyright (c) 2014-present Godot Engine contributors (see AUTHORS.md). */
|
|
|
|
/* Copyright (c) 2007-2014 Juan Linietsky, Ariel Manzur. */
|
2017-12-21 03:13:23 +01: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 12:46:36 +01:00
|
|
|
|
2022-07-23 23:41:51 +02:00
|
|
|
#ifndef WEBSOCKET_PEER_H
|
|
|
|
#define WEBSOCKET_PEER_H
|
2017-12-21 03:13:23 +01: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 22:44:44 +02:00
|
|
|
#include "core/crypto/crypto.h"
|
2020-11-07 23:33:38 +01:00
|
|
|
#include "core/error/error_list.h"
|
2017-12-21 03:13:23 +01:00
|
|
|
#include "core/io/packet_peer.h"
|
|
|
|
|
|
|
|
class WebSocketPeer : public PacketPeer {
|
|
|
|
GDCLASS(WebSocketPeer, PacketPeer);
|
|
|
|
|
|
|
|
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 22:44:44 +02:00
|
|
|
enum State {
|
|
|
|
STATE_CONNECTING,
|
|
|
|
STATE_OPEN,
|
|
|
|
STATE_CLOSING,
|
|
|
|
STATE_CLOSED
|
|
|
|
};
|
|
|
|
|
2017-12-21 03:13:23 +01:00
|
|
|
enum WriteMode {
|
|
|
|
WRITE_MODE_TEXT,
|
|
|
|
WRITE_MODE_BINARY,
|
|
|
|
};
|
|
|
|
|
[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 22:44:44 +02:00
|
|
|
enum {
|
|
|
|
DEFAULT_BUFFER_SIZE = 65535,
|
|
|
|
};
|
|
|
|
|
|
|
|
private:
|
|
|
|
virtual Error _send_bind(const PackedByteArray &p_data, WriteMode p_mode = WRITE_MODE_BINARY);
|
|
|
|
|
2017-12-21 03:13:23 +01:00
|
|
|
protected:
|
[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 22:44:44 +02:00
|
|
|
static WebSocketPeer *(*_create)();
|
|
|
|
|
2017-12-21 03:13:23 +01:00
|
|
|
static void _bind_methods();
|
|
|
|
|
[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 22:44:44 +02:00
|
|
|
Vector<String> supported_protocols;
|
|
|
|
Vector<String> handshake_headers;
|
|
|
|
|
|
|
|
Vector<String> _get_supported_protocols() const;
|
|
|
|
Vector<String> _get_handshake_headers() const;
|
|
|
|
|
|
|
|
int outbound_buffer_size = DEFAULT_BUFFER_SIZE;
|
|
|
|
int inbound_buffer_size = DEFAULT_BUFFER_SIZE;
|
|
|
|
int max_queued_packets = 2048;
|
|
|
|
|
2017-12-21 03:13:23 +01: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 22:44:44 +02:00
|
|
|
static WebSocketPeer *create() {
|
|
|
|
if (!_create) {
|
|
|
|
return nullptr;
|
|
|
|
}
|
|
|
|
return _create();
|
|
|
|
}
|
2017-12-21 03:13:23 +01:00
|
|
|
|
2023-01-20 01:51:35 +01:00
|
|
|
virtual Error connect_to_url(const String &p_url, Ref<TLSOptions> p_options = Ref<TLSOptions>()) = 0;
|
[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 22:44:44 +02:00
|
|
|
virtual Error accept_stream(Ref<StreamPeer> p_stream) = 0;
|
|
|
|
|
|
|
|
virtual Error send(const uint8_t *p_buffer, int p_buffer_size, WriteMode p_mode) = 0;
|
2018-09-23 21:14:20 +02:00
|
|
|
virtual void close(int p_code = 1000, String p_reason = "") = 0;
|
2017-12-21 03:13:23 +01:00
|
|
|
|
2021-05-06 02:48:18 +02:00
|
|
|
virtual IPAddress get_connected_host() const = 0;
|
2017-12-21 03:13:23 +01:00
|
|
|
virtual uint16_t get_connected_port() const = 0;
|
|
|
|
virtual bool was_string_packet() const = 0;
|
2020-01-28 14:06:28 +01:00
|
|
|
virtual void set_no_delay(bool p_enabled) = 0;
|
2021-07-29 22:11:27 +02:00
|
|
|
virtual int get_current_outbound_buffered_amount() const = 0;
|
[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 22:44:44 +02:00
|
|
|
virtual String get_selected_protocol() const = 0;
|
|
|
|
virtual String get_requested_url() const = 0;
|
|
|
|
|
|
|
|
virtual void poll() = 0;
|
|
|
|
virtual State get_ready_state() const = 0;
|
|
|
|
virtual int get_close_code() const = 0;
|
|
|
|
virtual String get_close_reason() const = 0;
|
|
|
|
|
|
|
|
Error send_text(const String &p_text);
|
|
|
|
|
|
|
|
void set_supported_protocols(const Vector<String> &p_protocols);
|
|
|
|
const Vector<String> get_supported_protocols() const;
|
|
|
|
|
|
|
|
void set_handshake_headers(const Vector<String> &p_headers);
|
|
|
|
const Vector<String> get_handshake_headers() const;
|
|
|
|
|
|
|
|
void set_outbound_buffer_size(int p_buffer_size);
|
|
|
|
int get_outbound_buffer_size() const;
|
|
|
|
|
|
|
|
void set_inbound_buffer_size(int p_buffer_size);
|
|
|
|
int get_inbound_buffer_size() const;
|
|
|
|
|
|
|
|
void set_max_queued_packets(int p_max_queued_packets);
|
|
|
|
int get_max_queued_packets() const;
|
2017-12-21 03:13:23 +01:00
|
|
|
|
|
|
|
WebSocketPeer();
|
|
|
|
~WebSocketPeer();
|
|
|
|
};
|
|
|
|
|
|
|
|
VARIANT_ENUM_CAST(WebSocketPeer::WriteMode);
|
[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 22:44:44 +02:00
|
|
|
VARIANT_ENUM_CAST(WebSocketPeer::State);
|
2022-07-23 23:41:51 +02:00
|
|
|
|
|
|
|
#endif // WEBSOCKET_PEER_H
|