Boost logo

Boost Users :

Subject: Re: [Boost-users] [boost][asio] Waiting on a returned value run in another strand
From: Brian Bartman (bbartmanboost_at_[hidden])
Date: 2018-01-24 12:53:50

All it really says is that there was a change to the interface, I'm really
looking for what that change really is. I keep trying to look for an
example within the ASIO code base but most of them are complicated, and not
really easy to follow/boil down what I need.

I did have one other question, that's semi-related to this, but is it
possible to yield a coroutine into a different strand, do something and
yield back to the original strand? If I can do this then I don't really
need to make the coroutine truly wait for a return value.

On Wed, Jan 24, 2018 at 1:11 AM, Gavin Lambert via Boost-users <
boost-users_at_[hidden]> wrote:

> On 24/01/2018 02:33, Brian Bartman wrote:
>> I'm trying to preform an asynchronous operation in order to obtain a
>> connection from a pool of available connections. I'm trying to leverage
>> strands for two reasons, 1) I don't need locks because I can guarantee that
>> the connection pool access is limited to quick sequential access, and 2) I
>> may need to wait for connections to become available, or I may need to
>> actually make a connection.
>> I'm working with the 1.66 version of boost and I have been searching the
>> internet for ANY answer to this question, so far none of the examples which
>> I've located work any more. All of them simply fail to compile. For example,
>> <
>> This uses an older version of boost.
>> So how can I do this under the newest version of boost.asio?
> I can't answer this directly since I haven't migrated to 1.66 yet myself,
> but you might find the following link to be of use:
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]

Brian Bartman

Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at