The translation has come to an end.
Zen

Translation

type: paragraph
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
193/1930 · 193

Sign in to save translations.

English Chinese (Simplified Han script) Actions
Design Choices
Design Choices
The implementations were originally driven by business needs of cryptocurrency server applications (e.g. [@https://github.com/ripple/rippled rippled]), written in C++. These needs were not met by existing solutions so Beast was written from scratch as a solution. Beast's design philosophy avoids flaws exhibited by other libraries:
The implementations were originally driven by business needs of cryptocurrency server applications (e.g. [@https://github.com/ripple/rippled rippled]), written in C++. These needs were not met by existing solutions so Beast was written from scratch as a solution. Beast's design philosophy avoids flaws exhibited by other libraries:
* Don't try to do too much.
* Don't try to do too much.
* Don't sacrifice performance.
* Don't sacrifice performance.
* Mimic __Asio__; familiarity breeds confidence.
* Mimic __Asio__; familiarity breeds confidence.
* Role-symmetric interfaces; client and server the same (or close to it).
* Role-symmetric interfaces; client and server the same (or close to it).
* Leave important decisions, such as allocating memory or
* Leave important decisions, such as allocating memory or
Beast uses the __DynamicBuffer__ concept presented in the __NetTS__, and relies heavily on the __ConstBufferSequence__ and __MutableBufferSequence__ concepts for passing buffers to functions. The authors have found the dynamic buffer and buffer sequence interfaces to be optimal for interacting with Asio, and for other tasks such as incremental parsing of data in buffers (for example, parsing websocket frames stored in a [link beast.ref.boost__beast__static_buffer `static_buffer`]).
Beast uses the __DynamicBuffer__ concept presented in the __NetTS__, and relies heavily on the __ConstBufferSequence__ and __MutableBufferSequence__ concepts for passing buffers to functions. The authors have found the dynamic buffer and buffer sequence interfaces to be optimal for interacting with Asio, and for other tasks such as incremental parsing of data in buffers (for example, parsing websocket frames stored in a [link beast.ref.boost__beast__static_buffer `static_buffer`]).
During the development of Beast the authors have studied other software packages and in particular the comments left during the Boost Review process of other packages offering similar functionality. In this section and the FAQs that follow we attempt to answer those questions that are also applicable to Beast.
During the development of Beast the authors have studied other software packages and in particular the comments left during the Boost Review process of other packages offering similar functionality. In this section and the FAQs that follow we attempt to answer those questions that are also applicable to Beast.
For HTTP we model the message to maximize flexibility of implementation strategies while allowing familiar verbs such as [*`read`] and [*`write`]. The HTTP interface is further driven by the needs of the WebSocket module, as a WebSocket session requires a HTTP Upgrade handshake exchange at the start. Other design goals:
For HTTP we model the message to maximize flexibility of implementation strategies while allowing familiar verbs such as [*`read`] and [*`write`]. The HTTP interface is further driven by the needs of the WebSocket module, as a WebSocket session requires a HTTP Upgrade handshake exchange at the start. Other design goals:
* Keep it simple.
* Keep it simple.
* Stay low level; don't invent a whole web server or client.
* Stay low level; don't invent a whole web server or client.
* Allow for customizations, if the user needs it.
* Allow for customizations, if the user needs it.
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
English Chinese (Simplified Han script) Actions
Design Choices
Design Choices
The implementations were originally driven by business needs of cryptocurrency server applications (e.g. [@https://github.com/ripple/rippled rippled]), written in C++. These needs were not met by existing solutions so Beast was written from scratch as a solution. Beast's design philosophy avoids flaws exhibited by other libraries:
The implementations were originally driven by business needs of cryptocurrency server applications (e.g. [@https://github.com/ripple/rippled rippled]), written in C++. These needs were not met by existing solutions so Beast was written from scratch as a solution. Beast's design philosophy avoids flaws exhibited by other libraries:
* Don't try to do too much.
* Don't try to do too much.
* Don't sacrifice performance.
* Don't sacrifice performance.
* Mimic __Asio__; familiarity breeds confidence.
* Mimic __Asio__; familiarity breeds confidence.
* Role-symmetric interfaces; client and server the same (or close to it).
* Role-symmetric interfaces; client and server the same (or close to it).
* Leave important decisions, such as allocating memory or
* Leave important decisions, such as allocating memory or
Beast uses the __DynamicBuffer__ concept presented in the __NetTS__, and relies heavily on the __ConstBufferSequence__ and __MutableBufferSequence__ concepts for passing buffers to functions. The authors have found the dynamic buffer and buffer sequence interfaces to be optimal for interacting with Asio, and for other tasks such as incremental parsing of data in buffers (for example, parsing websocket frames stored in a [link beast.ref.boost__beast__static_buffer `static_buffer`]).
Beast uses the __DynamicBuffer__ concept presented in the __NetTS__, and relies heavily on the __ConstBufferSequence__ and __MutableBufferSequence__ concepts for passing buffers to functions. The authors have found the dynamic buffer and buffer sequence interfaces to be optimal for interacting with Asio, and for other tasks such as incremental parsing of data in buffers (for example, parsing websocket frames stored in a [link beast.ref.boost__beast__static_buffer `static_buffer`]).
During the development of Beast the authors have studied other software packages and in particular the comments left during the Boost Review process of other packages offering similar functionality. In this section and the FAQs that follow we attempt to answer those questions that are also applicable to Beast.
During the development of Beast the authors have studied other software packages and in particular the comments left during the Boost Review process of other packages offering similar functionality. In this section and the FAQs that follow we attempt to answer those questions that are also applicable to Beast.
For HTTP we model the message to maximize flexibility of implementation strategies while allowing familiar verbs such as [*`read`] and [*`write`]. The HTTP interface is further driven by the needs of the WebSocket module, as a WebSocket session requires a HTTP Upgrade handshake exchange at the start. Other design goals:
For HTTP we model the message to maximize flexibility of implementation strategies while allowing familiar verbs such as [*`read`] and [*`write`]. The HTTP interface is further driven by the needs of the WebSocket module, as a WebSocket session requires a HTTP Upgrade handshake exchange at the start. Other design goals:
* Keep it simple.
* Keep it simple.
* Stay low level; don't invent a whole web server or client.
* Stay low level; don't invent a whole web server or client.
* Allow for customizations, if the user needs it.
* Allow for customizations, if the user needs it.
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).

Loading…

User avatar admin

String added in the repository
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
The following video presentation was delivered at [@https://cppcon.org/ CppCon] in 2016. It provides a light introduction to some of the earliest interfaces of Beast (which have since changed).
06/05/2026
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical.

Reset

Glossary

English Chinese (Simplified Han script)
No related strings found in the glossary.

String information

Source string description
type: paragraph
Unit identifier
58848
Source string location
string ID 55
String age
06/05/2026
Last updated
06/05/2026
Source string age
06/05/2026
Translation file QuickBook file
doc/qbk/08_design/_design_zh_Hans.qbk, string 14