Re: [Capy/Corosio] Review
Steve Gerbino via Boost <[email protected]> Fri, 03 Jul 2026 15:56:00 +0000
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <kt7zvUSuVNwJStlU1KEesQdWXscZsT2zvq4EIL2OaIjL5ERf7t2alJ24CScTVxeICZmruqXU0j_-1b37mA1uYmS9Q03WhiCrp5sSr-sSrQs=@gerbino.co> |
On Friday, July 3rd, 2026 at 7:17 AM, Jamie Allsop via Boost <[email protected]> wrote: > A quick review of the documentation reveals a number of such libraries, > planned or otherwise: > > - Corosio — portable coroutine networking (this review) > - Http — sans-I/O HTTP/1.1 clients and servers > - Websocket — sans-I/O WebSocket > - Beast2 — high-level HTTP/WebSocket servers > - Burl — high-level HTTP client > > Note to the authors - I’d like to see links to these libraries in the > docs - even if that directs to a “coming soon” page or repo under > development. For our needs we’d definitely be looking to utilise > WebSocket functionality that allows us to replace (or integrate with) Duly noted. > 3. Both: If you make a strong statement in the Introduction please make > sure you reference and link to where in the documentation you actually > explain that and why it matters. For example, in the Corosio > introduction it says, "...that provides asynchronous networking > primitives with automatic executor affinity propagation". Interesting > for sure but given this is the opening sentence about why I should care > I'd hoped to be able to read more about this and why I should care and > what that means for me, the user. I see this as a missed opportunity. Fair point, we'll definitely keep this in mind while improving the documentation. > I would note also I had to figure out how to build the documentation > since that’s not covered. I added it to the README of my local copy. If you are so included, I'd happily merge this upstream. > Finally, given my only personal concerns for acceptance were > documentation updates, which I see the authors are already committed to, > I don’t feel the need to do a further review of that before acceptance. > I trust it will happen, so: > > +----------------------------------------------------+ > | I vote for the libraries to be ACCEPTED into Boost | > +----------------------------------------------------+ > > Best wishes, > Jamie I appreciate you taking the time to write about your implementation experience. Thanks for the review and all the points of improvement you've laid out. _______________________________________________ Boost mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/[email protected]/message/JK3W7HT7WMWTXWM2DMVXGA2KJOQT6SMS/