Subject: Re: [boost] Asynchronous library now in Boost Library Incubator
From: Christophe Henry (christophe.j.henry_at_[hidden])
Date: 2016-12-06 15:09:12
On 12/06/2016 03:55 PM, Thomas Heller wrote:
> On Dienstag, 6. Dezember 2016 15:44:39 CET you wrote:
>> On Donnerstag, 1. Dezember 2016 21:45:52 CET Christophe Henry wrote:
>>>> I didn't quite understand the state machine explanation - but I'll
>>>> continue looking through the boost.asynchronous material until I am
>>> I tried to add an example and the underlying rationale
>>> lo b/master/libs/asynchronous/doc/asynchronous.html#d0e6437).
>>> The Manager is a very simplified state machine but I hope you get the
>> When looking at the example code, doesn't it contain a race on
>> Manager::needs_second_task member. If not, how is it avoided?
> So in this example, the race is avoided because it uses a single thread
> scheduler as the "thread world", right?
And because you use a proxy and post_callback.
>What happens if I'd change it to run
> on multiple threads?
In this case you'd have to synchronize and it would make little sense,
which is why servants are usually used within a single thread world.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk