Re: [Boost-users] Boost.Beast vs Boost.Asio

Subject: Re: [Boost-users] Boost.Beast vs Boost.Asio
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2018-12-04 14:24:43

> -----Original Message-----
> From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On Behalf Of Vinnie Falco via Boost-users
> Sent: 04 December 2018 13:47
> To: boost-users_at_[hidden]
> Cc: Vinnie Falco
> Subject: Re: [Boost-users] Boost.Beast vs Boost.Asio
> 
> On Tue, Dec 4, 2018 at 2:50 AM Paul A. Bristow via Boost-users
> <boost-users_at_[hidden]> wrote:
> > Do 'see also' links of the form
> >
> > https://www.boost.org/doc/libs/release/doc/html/other_library/...  help here
> >
> > help in resolving this?
> >
> > Both libraries could (should even) helpfully cross-link each other?
> 
> Beast documentation has extensive cross-links to Boost.Asio docs, for
> example click on return type ("DEDUCED") of these function signatures:
> 
> <https://www.boost.org/doc/libs/1_68_0/libs/beast/doc/html/beast/ref/boost__beast__http__async_read.html>
> 
> > A PR that is just a link is much more likely to be accepted than something that needs real effort?
> 
> I don't know that it makes sense for asio to link back to beast. And
> that wouldn't be meaningful for the stand-alone version (which shares
> the same docs).

It is usually best to link to  https://www.boost.org/doc/libs/release/libs/beast ... rather than a Boost release version-specific
link

like https://www.boost.org/doc/libs/1_68_0/libs/beast/doc/html/beast/...

But perhaps you knew and do that already?

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]