[review][beast] Review of Beast starts today : July 1 - July 10

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[review][beast] Review of Beast starts today : July 1 - July 10

Boost - Users mailing list
The formal review of Vinnie Falco’s Beast library will take place from
July 1 through July 10, 2017.

Please consider participating in this review. The success of Boost is
partially a result of the quality review process which is conducted by
the community. You are part of the Boost community. I will be grateful
to receive a review based on whatever level of effort or time you can
devote.

Beast is a C++ header-only library serving as a foundation for writing
interoperable networking libraries by providing low-level HTTP/1,
WebSocket, and networking protocol vocabulary types and algorithms using
the consistent asynchronous model of Boost.Asio.

Beast is designed for:

  * Symmetry: Algorithms are role-agnostic; build clients, servers, or
    both.
  * Ease of Use: Boost.Asio users will immediately understand Beast.
  * Flexibility: Users make the important decisions such as buffer or
    thread management.
  * Performance: Build applications handling thousands of connections
    or more.
  * Basis for Further Abstraction: Components are well-suited for
    building upon.

A branch has been made for the review. You can find Beast for review at
these links:

  * Documentation : <http://vinniefalco.github.io/stage/beast/review/>
  * Source code : <https://github.com/vinniefalco/Beast/tree/review>
  * The FAQ answers real questions that come up :

<http://vinniefalco.github.io/stage/beast/review/beast/design_choices/faq.html>

A lightning talk from CppCon 2016 introducing Beast can be found here:
<https://www.youtube.com/watch?v=uJZgRcvPFwI>


Please provide in your review whatever information you think is valuable
to understand your final choice of ACCEPT or REJECT including Beast as a
Boost library. Please be explicit about your decision.

Some other questions you might want to consider answering:

  - What is your evaluation of the design?
  - What is your evaluation of the implementation?
  - What is your evaluation of the documentation?
  - What is your evaluation of the potential usefulness of the library?
  - Did you try to use the library? With which compiler(s)? Did you
    have any problems?
  - How much effort did you put into your evaluation? A glance? A quick
    reading? In-depth study?
  - Are you knowledgeable about the problem domain?

More information about the Boost Formal Review Process can be found
here: <http://www.boost.org/community/reviews.html>

Thank you for your effort in the Boost community.

Happy coding -
michael

--
Michael Caisse
Ciere Consulting
ciere.com
_______________________________________________
Boost-users mailing list
[hidden email]
https://lists.boost.org/mailman/listinfo.cgi/boost-users
Loading...