2017-06-03 18:40:28 -07:00
|
|
|
[/
|
|
|
|
|
Copyright (c) 2013-2017 Vinnie Falco (vinnie dot falco at gmail dot com)
|
|
|
|
|
|
|
|
|
|
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)
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
[section:websocket Using WebSocket]
|
|
|
|
|
|
|
|
|
|
The WebSocket Protocol enables two-way communication between a client
|
|
|
|
|
running untrusted code in a controlled environment to a remote host that has
|
|
|
|
|
opted-in to communications from that code. The protocol consists of an opening
|
|
|
|
|
handshake followed by basic message framing, layered over TCP. The goal of
|
|
|
|
|
this technology is to provide a mechanism for browser-based applications
|
|
|
|
|
needing two-way communication with servers without relying on opening multiple
|
|
|
|
|
HTTP connections.
|
|
|
|
|
|
|
|
|
|
Beast provides developers with a robust WebSocket implementation built on
|
|
|
|
|
Boost.Asio with a consistent asynchronous model using a modern C++ approach.
|
|
|
|
|
|
|
|
|
|
[note
|
|
|
|
|
The WebSocket documentation assumes familiarity the WebSocket protocol
|
|
|
|
|
specification described in __rfc6455__. Code appearing in these
|
|
|
|
|
sections is written as if the following declarations are in effect:
|
|
|
|
|
```
|
|
|
|
|
#include <beast/websocket.hpp>
|
|
|
|
|
```
|
|
|
|
|
]
|
|
|
|
|
|
2017-06-04 17:25:55 -07:00
|
|
|
[include 6_1_streams.qbk]
|
|
|
|
|
[include 6_2_connect.qbk]
|
|
|
|
|
[include 6_3_client.qbk]
|
|
|
|
|
[include 6_4_server.qbk]
|
|
|
|
|
[include 6_5_messages.qbk]
|
|
|
|
|
[include 6_6_control.qbk]
|
|
|
|
|
[include 6_7_notes.qbk]
|
2017-06-03 18:40:28 -07:00
|
|
|
|
|
|
|
|
[endsect]
|
