Exit Zen
48
string ID 256
type: list
English
* Use `span` from Boost.Core
* Use `static_string` from Boost.StaticString
* `serializer::is_done` is `const`
* Support for default-completion and rebind
* [issue 2469] s390x architecture support
195/1950 · 195
48
string ID 175
type: table cell
English
prepare/commit
14/140 · 14
48
string ID 345
type: paragraph
English
response<file_body> res; ```
28/280 · 28
48
string ID 203
type: paragraph
English
Server example: [path_link example/doc/ssl/server.cpp server.cpp]
65/650 · 65
49
string ID 109
type: table cell
English
[path_link example/http/server/async/http_server_async.cpp http_server_async.cpp]
81/810 · 81
49
string ID 383
type: table cell
English
A variable of type [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `tcp::socket`] which has already been connected to a remote host.
143/1430 · 143
214
string ID 214
type: table cell
English
Statements
10/100 · 10
49
string ID 264
type: list
English
* [issue 891] Feature table for buffers
* [issue 516] Case-insensitivity for fields is stated
* [issue 298] api version is documented
133/1330 · 133
49
string ID 309
type: paragraph
English
To understand these declarations we need to first understand that cpprestsdk uses the asynchronous model defined by Microsoft's [@https://msdn.microsoft.com/en-us/library/dd504870.aspx [*Concurrency Runtime]]. Identifiers from the [@https://msdn.microsoft.com/en-us/library/jj987780.aspx [*`pplx` namespace]] define common asynchronous patterns such as tasks and events. The `concurrency::streams::istream` parameter and `m_data_available` data member indicates a lack of separation of concerns. The representation of HTTP messages should not be conflated with the asynchronous model used to serialize or parse those messages in the message declarations.
654/6540 · 654
49
string ID 175
type: table cell
English
consume
7/100 · 7
49
string ID 348
type: paragraph
English
This container is also capable of representing complete HTTP/2 messages. Not because it was explicitly designed for, but because the IETF wanted to preserve message compatibility with HTTP/1. Aside from version specific fields such as Connection, the contents of HTTP/1 and HTTP/2 messages are identical even though their serialized representation is considerably different. The message model presented in this library is ready for HTTP/2.
439/4390 · 439
49
string ID 205
type: paragraph
English
Note that the server is configured in such a way that it requests and verifies the client certificate. You can disable this by commenting out the related line in the example.
174/1740 · 174
50
string ID 109
type: table cell
English
[path_link example/http/server/async-ssl/http_server_async_ssl.cpp http_server_async_ssl.cpp]
93/930 · 93
50
string ID 383
type: table cell
English
[@boost:/doc/html/boost_asio/reference/ssl__stream.html [*`ssl_sock`]]
70/700 · 70
214
string ID 214
type: table cell
English
Serialized Result
17/170 · 17
50
string ID 319
type: paragraph
English
The next declaration forms the complete implementation class referenced by the handle in the public interface (which follows after): ``` /// Internal representation of an HTTP request message. class _http_request final : public http::details::http_msg_base, public std::enable_shared_from_this<_http_request> { public:
318/3180 · 318
50
string ID 175
type: table cell
English
[link beast.ref.boost__beast__flat_buffer `flat_buffer`]
56/560 · 56
50
string ID 355
type: paragraph
English
In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere.
389/3890 · 389
50
string ID 209
type: paragraph
English
You can test the server using this cURL command:
48/480 · 48
109
string ID 109
type: table cell
English
HTTP, asynchronous Unix domain sockets
38/380 · 38