This is the mail archive of the
mailing list for the libstdc++ project.
Re: Networking TS implementation
- From: Mikhail Maltsev <maltsevm at gmail dot com>
- To: Jonathan Wakely <jwakely at redhat dot com>, libstdc++ at gcc dot gnu dot org
- Date: Sat, 17 Oct 2015 21:40:46 +0300
- Subject: Re: Networking TS implementation
- Authentication-results: sourceware.org; auth=none
- References: <20151017154615 dot GH12094 at redhat dot com>
On 10/17/2015 06:46 PM, Jonathan Wakely wrote:
> It's still missing socket iostreams, parts of the use_future
> completion token handling, and system_context needs some work
> (currently it uses a "thread pool" hardcoded to one thread).
Hi! I'm very interested in the networking part of the C++ standard, but
unfortunately could not find much information on it's current status.
Perhaps you could help and shed some light on the situation:
1. Do I understand correctly, that the library part (especially the API) is
mostly based on the asio  library?
2. What about futures/promises, i.e. some facilities for chaining async_result-s
(IIUC, current std::future will not work well with asio Executor-s)? Will the
standard eventually include something similar to tasks implemented in
Microsoft's casablanca (aka cpprestsdk)  or futures/promises in the seastar
3. What about resumable functions support in the language itself? Which
implementation is in favor? Is it N4134 ?
4. How will all of the above work together?