This is the mail archive of the mailing list for the libstdc++ project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Networking TS implementation

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 [1] 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) [2] or futures/promises in the seastar
library [3]?
3. What about resumable functions support in the language itself? Which
implementation is in favor? Is it N4134 [4]?
4. How will all of the above work together?


    Mikhail Maltsev

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]