Files
boost_beast/include/beast/websocket/option.hpp

328 lines
8.5 KiB
C++
Raw Normal View History

2017-07-20 08:01:46 -07:00
//
2017-02-06 20:07:03 -05:00
// Copyright (c) 2013-2017 Vinnie Falco (vinnie dot falco at gmail dot com)
2017-07-20 08:01:46 -07:00
//
// Distributed under the Boost Software License, Version 1.0. (See accompanying
// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
//
#ifndef BEAST_WEBSOCKET_OPTION_HPP
#define BEAST_WEBSOCKET_OPTION_HPP
#include <beast/config.hpp>
#include <beast/websocket/rfc6455.hpp>
#include <beast/core/detail/type_traits.hpp>
2017-07-20 08:01:46 -07:00
#include <algorithm>
#include <cstdint>
2016-10-24 20:02:38 -04:00
#include <functional>
2017-07-20 08:01:46 -07:00
#include <stdexcept>
#include <type_traits>
#include <utility>
2017-07-20 08:01:46 -07:00
namespace beast {
namespace websocket {
2016-06-10 15:48:39 -04:00
/** Automatic fragmentation option.
2017-07-20 08:01:46 -07:00
2016-06-10 15:48:39 -04:00
Determines if outgoing message payloads are broken up into
multiple pieces.
2017-07-20 08:01:46 -07:00
2016-06-10 15:48:39 -04:00
When the automatic fragmentation size is turned on, outgoing
message payloads are broken up into multiple frames no larger
than the write buffer size.
2017-07-20 08:01:46 -07:00
2016-06-10 15:48:39 -04:00
The default setting is to fragment messages.
2017-07-20 08:01:46 -07:00
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
2017-07-20 08:01:46 -07:00
@par Example
2016-06-10 15:48:39 -04:00
Setting the automatic fragmentation option:
2017-07-20 08:01:46 -07:00
@code
...
websocket::stream<ip::tcp::socket> stream(ios);
2016-06-10 15:48:39 -04:00
stream.set_option(auto_fragment{true});
2017-07-20 08:01:46 -07:00
@endcode
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
2016-06-10 15:48:39 -04:00
using auto_fragment = implementation_defined;
2017-07-20 08:01:46 -07:00
#else
2016-06-10 15:48:39 -04:00
struct auto_fragment
2017-07-20 08:01:46 -07:00
{
2016-06-10 15:48:39 -04:00
bool value;
2017-07-20 08:01:46 -07:00
2016-06-10 15:48:39 -04:00
explicit
auto_fragment(bool v)
: value(v)
2017-07-20 08:01:46 -07:00
{
}
};
#endif
/** Message type option.
This controls the opcode set for outgoing messages. Valid
choices are opcode::binary or opcode::text. The setting is
only applied at the start when a caller begins a new message.
Changing the opcode after a message is started will only
take effect after the current message being sent is complete.
The default setting is opcode::text.
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
2017-07-20 08:01:46 -07:00
@par Example
Setting the message type to binary.
@code
...
websocket::stream<ip::tcp::socket> ws(ios);
ws.set_option(message_type{opcode::binary});
@endcode
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
2017-07-20 08:01:46 -07:00
using message_type = implementation_defined;
#else
struct message_type
{
opcode value;
explicit
message_type(opcode op)
{
if(op != opcode::binary && op != opcode::text)
throw beast::detail::make_exception<std::invalid_argument>(
"bad opcode", __FILE__, __LINE__);
2017-07-20 08:01:46 -07:00
value = op;
}
};
#endif
2016-10-24 20:02:38 -04:00
namespace detail {
using ping_cb = std::function<void(bool, ping_data const&)>;
2016-10-24 20:02:38 -04:00
} // detail
/** permessage-deflate extension options.
These settings control the permessage-deflate extension,
which allows messages to be compressed.
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
*/
struct permessage_deflate
{
/// `true` to offer the extension in the server role
bool server_enable = false;
/// `true` to offer the extension in the client role
bool client_enable = false;
/** Maximum server window bits to offer
2017-02-06 20:07:03 -05:00
@note Due to a bug in ZLib, this value must be greater than 8.
*/
int server_max_window_bits = 15;
/** Maximum client window bits to offer
2017-02-06 20:07:03 -05:00
@note Due to a bug in ZLib, this value must be greater than 8.
*/
int client_max_window_bits = 15;
/// `true` if server_no_context_takeover desired
bool server_no_context_takeover = false;
/// `true` if client_no_context_takeover desired
bool client_no_context_takeover = false;
/// Deflate compression level 0..9
int compLevel = 8;
/// Deflate memory level, 1..9
int memLevel = 4;
};
/** Ping callback option.
Sets the callback to be invoked whenever a ping or pong is
2017-02-07 19:11:24 -05:00
received during a call to one of the following functions:
@li @ref beast::websocket::stream::read
@li @ref beast::websocket::stream::read_frame
@li @ref beast::websocket::stream::async_read
@li @ref beast::websocket::stream::async_read_frame
Unlike completion handlers, the callback will be invoked
for each received ping and pong during a call to any
synchronous or asynchronous read function. The operation is
passive, with no associated error code, and triggered by reads.
The signature of the callback must be:
@code
void
callback(
bool is_pong, // `true` if this is a pong
ping_data const& payload // Payload of the pong frame
);
@endcode
The value of `is_pong` will be `true` if a pong control frame
is received, and `false` if a ping control frame is received.
If the read operation receiving a ping or pong frame is an
asynchronous operation, the callback will be invoked using
the same method as that used to invoke the final handler.
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
To remove the ping callback, construct the option with
no parameters: `set_option(ping_callback{})`
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
using ping_callback = implementation_defined;
#else
struct ping_callback
{
detail::ping_cb value;
ping_callback() = default;
ping_callback(ping_callback&&) = default;
ping_callback(ping_callback const&) = default;
explicit
ping_callback(detail::ping_cb f)
: value(std::move(f))
{
}
};
#endif
2017-07-20 08:01:46 -07:00
/** Read buffer size option.
Sets the size of the read buffer used by the implementation to
receive frames. The read buffer is needed when permessage-deflate
is used.
Lowering the size of the buffer can decrease the memory requirements
for each connection, while increasing the size of the buffer can reduce
the number of calls made to the next layer to read data.
2017-07-20 08:01:46 -07:00
The default setting is 4096. The minimum value is 8.
2017-07-20 08:01:46 -07:00
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
2017-07-20 08:01:46 -07:00
@par Example
Setting the read buffer size.
@code
...
websocket::stream<ip::tcp::socket> ws(ios);
ws.set_option(read_buffer_size{16 * 1024});
@endcode
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
2017-07-20 08:01:46 -07:00
using read_buffer_size = implementation_defined;
#else
struct read_buffer_size
{
std::size_t value;
explicit
read_buffer_size(std::size_t n)
: value(n)
{
if(n < 8)
throw beast::detail::make_exception<std::invalid_argument>(
"read buffer size is too small", __FILE__, __LINE__);
2017-07-20 08:01:46 -07:00
}
};
#endif
/** Maximum incoming message size option.
Sets the largest permissible incoming message size. Message
frame fields indicating a size that would bring the total
2017-07-20 08:01:46 -07:00
message size over this limit will cause a protocol failure.
The default setting is 16 megabytes. A value of zero indicates
a limit of the maximum value of a `std::uint64_t`.
2017-07-20 08:01:46 -07:00
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
2017-07-20 08:01:46 -07:00
@par Example
Setting the maximum read message size.
@code
...
websocket::stream<ip::tcp::socket> ws(ios);
ws.set_option(read_message_max{65536});
@endcode
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
2017-07-20 08:01:46 -07:00
using read_message_max = implementation_defined;
#else
struct read_message_max
{
std::size_t value;
explicit
read_message_max(std::size_t n)
: value(n)
{
}
};
#endif
2016-06-10 13:20:41 -04:00
/** Write buffer size option.
Sets the size of the write buffer used by the implementation to
send frames. The write buffer is needed when masking payload data
in the client role, compressing frames, or auto-fragmenting message
data.
Lowering the size of the buffer can decrease the memory requirements
for each connection, while increasing the size of the buffer can reduce
the number of calls made to the next layer to write data.
2016-06-10 15:48:39 -04:00
The default setting is 4096. The minimum value is 8.
The write buffer size can only be changed when the stream is not
open. Undefined behavior results if the option is modified after a
successful WebSocket handshake.
2016-06-10 13:20:41 -04:00
@note Objects of this type are used with
@ref beast::websocket::stream::set_option.
2016-06-10 13:20:41 -04:00
@par Example
Setting the write buffer size.
@code
...
websocket::stream<ip::tcp::socket> ws(ios);
ws.set_option(write_buffer_size{8192});
@endcode
*/
2017-04-22 14:56:09 -07:00
#if BEAST_DOXYGEN
2016-06-10 13:20:41 -04:00
using write_buffer_size = implementation_defined;
#else
struct write_buffer_size
{
std::size_t value;
explicit
write_buffer_size(std::size_t n)
: value(n)
{
2016-06-10 15:48:39 -04:00
if(n < 8)
throw beast::detail::make_exception<std::invalid_argument>(
"write buffer size is too small", __FILE__, __LINE__);
2016-06-10 13:20:41 -04:00
}
};
#endif
2017-07-20 08:01:46 -07:00
} // websocket
} // beast
#endif