Documentation tidy

This commit is contained in:
Vinnie Falco
2017-06-15 01:10:50 -07:00
parent 510092d34b
commit 2bbb8ab8a2
2 changed files with 13 additions and 23 deletions

View File

@ -13,7 +13,6 @@
## Contents ## Contents
- [Introduction](#introduction) - [Introduction](#introduction)
- [Audience](audience)
- [Appearances](#appearances) - [Appearances](#appearances)
- [Description](#description) - [Description](#description)
- [Requirements](#requirements) - [Requirements](#requirements)
@ -25,18 +24,14 @@
## Introduction ## Introduction
Beast is a cross-platform, header-only C++11 library for low-level Beast is a C++ header-only library serving as a foundation for writing
HTTP/1 and WebSocket protocol programming interoperable networking libraries by providing **low-level HTTP/1,
using the consistent asynchronous networking model of Boost.Asio. WebSocket, and networking protocol** vocabulary types and algorithms
Beast is not an HTTP client or HTTP server, but it can be used to using the consistent asynchronous model of Boost.Asio.
build those things. It is intended to be a foundation for writing
other interoperable libraries by providing HTTP vocabulary types
and algorithms. The provided examples show how clients and servers
might be built.
This library is designed for: This library is designed for:
* **Symmetry:** Interfaces are role-agnostic; build clients, servers, or both. * **Symmetry:** Algorithms are role-agnostic; build clients, servers, or both.
* **Ease of Use:** Boost.Asio users will immediately understand Beast. * **Ease of Use:** Boost.Asio users will immediately understand Beast.
@ -45,16 +40,7 @@ This library is designed for:
* **Performance:** Build applications handling thousands of connections or more. * **Performance:** Build applications handling thousands of connections or more.
* **Basis for Further Abstraction.** Components are open-ended and * **Basis for Further Abstraction.** Components are well-suited for building upon.
suited for building higher level libraries.
## Audience
Beast is for network programmers who have some familiarity with
Boost.Asio. In particular, users who wish to write asynchronous programs
with Beast should already know how to use Asio sockets and streams,
and should know how to create concurrent network programs using
Asio callbacks or coroutines.
## Appearances ## Appearances
@ -76,6 +62,10 @@ The library has been submitted to the
## Requirements ## Requirements
This library is for programmers familiar with Boost.Asio. Users
who wish to use asynchronous interfaces should already know how to
create concurrent network programs using callbacks or coroutines.
* **C++11:** Robust support for most language features. * **C++11:** Robust support for most language features.
* **Boost:** Boost.Asio and some other parts of Boost. * **Boost:** Boost.Asio and some other parts of Boost.
* **OpenSSL:** Optional, for using TLS/Secure sockets. * **OpenSSL:** Optional, for using TLS/Secure sockets.
@ -146,7 +136,7 @@ The files in the repository are laid out thusly:
include/ Add this to your compiler includes include/ Add this to your compiler includes
beast/ beast/
extras/ Additional APIs, may change extras/ Additional APIs, may change
examples/ Self contained example programs example/ Self contained example programs
test/ Unit tests and benchmarks test/ Unit tests and benchmarks
``` ```

View File

@ -42,7 +42,7 @@ In this table:
[`X(f,v,m)`] [`X(f,v,m)`]
[] []
[ [
The implementatation uses this constructor to indicate The implementation calls this constructor to indicate
that the fields being serialized form part of an HTTP that the fields being serialized form part of an HTTP
request. The lifetime of `f` is guaranteed request. The lifetime of `f` is guaranteed
to end no earlier than after the `X` is destroyed. to end no earlier than after the `X` is destroyed.
@ -51,7 +51,7 @@ In this table:
[`X(f,v,c)`] [`X(f,v,c)`]
[] []
[ [
The implementatation uses this constructor to indicate The implementation calls this constructor to indicate
that the fields being serialized form part of an HTTP that the fields being serialized form part of an HTTP
response. The lifetime of `f` is guaranteed response. The lifetime of `f` is guaranteed
to end no earlier than after the `X` is destroyed. to end no earlier than after the `X` is destroyed.