Re: [boost] [asio] demuxer::post restrictions?

From: Jeff Flinn (TriumphSprint2000_at_[hidden])
Date: 2006-02-27 09:03:41

Christopher Kohlhoff wrote:
> Hi Jeff,
>
> --- Jeff Flinn <TriumphSprint2000_at_[hidden]> wrote:
>> Can demuxer::post be safely called from a thread different
>> from the thread from which demuxer::run is called?
>
> Yep.
>
>> It's not clear from the docs, or I'm missing it.
>
> Most of the classes have a "Thread Safety" section in their
> documentation. For the demuxer it reads:
>
>  Distinct objects: Safe.
>
>  Shared objects: Safe, with the exception that calling reset()
>  while there are unfinished run() calls results in undefined
>  behaviour.
>
> This means that any of the demuxer functions can be called from
> any thread at any time, with the noted exception of reset().

Now that you point it out I don't know how I missed that. :-o I'm now trying 
to convert one of our synchronous communication libraries to asynch using 
asio. The examples seem so straightforward, but thinking in terms of asynch 
operations on a 'fresh' application is challenging.

Thanks, Jeff