Re: [Boost-users] Boost::Asio No write handler called after async_write

Subject: Re: [Boost-users] Boost::Asio No write handler called after async_write
From: David Narvaez (david.e.narvaez_at_[hidden])
Date: 2009-04-14 23:17:24

Thanks! Working like a charm now.

David E. Narváez

On Tue, Apr 14, 2009 at 11:15 AM, Igor R <boost.lists_at_[hidden]> wrote:

> > Thanks for the answer, but all examples I see in the documentation using
> > io_service:::run() are using an async-read/async-write model. How would
> > io_service::run() fit in my sync-read/async-write model? Or is it
> impossible
> > to do async-write if using async-read?
>
> I don't see in your code snippet where you intend to perform
> sync.read. Anyway, there's no technical limitation to use both
> sync.read and async.write - for example, you can call sync.read in
> handle_write, and it will work. As for io_service::run, you can place
> it just before "return" in Server::run.
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>