Re: [Boost-users] blocking read after async connect

Subject: Re: [Boost-users] blocking read after async connect
From: David Kaplan (davkaplan_at_[hidden])
Date: 2010-03-22 05:26:57

>
> > I have a class that performs a timed connect (i.e. using an async connect
> > that returns an error if connection failed/timed-out).
> > However every asio::read/write performed on the socket after a successful
> > async_connect fails.
> >
> > Any ideas? Is it impossible to perform read/write on such a socket? do I
> > have to stop() the io service to put it back into synchronous mode?
>
> AFAIK, there's no problem to mix sync./async. operations this way.
> What do you mean by saying "fails"? What error/exception do you
> encounter?
>

I find that unless I call io_service::stop() , I can't perform a
asio::read().
It's actually on a thread and I'm having difficulty seeing what the
exception thrown exactly is ('thread called terminate')