Re: [Boost-users] [asio] Callbacks not getting called
So, I tried it, but surprisingly, it didn't make any difference. I'm not sure why there wasn't an error, it seems like one of HandleAccept and &HandleAccept would cause some type of error. Also, I'm not having the problem getting through the acceptor. The server successfully gets the accept callback for the connection from the client (and the client gets its callback as well). Its the aysnc_send/async_read that doesn't ever get a callback. I tried using the reference to HandleAccept in those as well, but like I said above, saw the *exact* same results. Tom -------- Original Message -------- Subject: Re: [Boost-users] [asio] Callbacks not getting called From: Rutger ter Borg (rutger_at_[hidden]) Date: 2010-03-11 16:55:43 Tom Kent wrote:
acceptor_->async_accept(*sock1_, HandleAccept);
Perhaps you could try acceptor_->async_accept(*sock1_, &HandleAccept); here? Cheers, Rutger
Its the aysnc_send/async_read that doesn't ever get a callback. I tried using the reference to HandleAccept in those as well, but like I said above, saw the *exact* same results.
If handlers don't get called - it usually means that io_service
stopped. Try wrapping io_service::run() with your own thread function
to see what happens:
void do_run(io_service *io)
{
io->run();
std::cout << "io_service::run ended" <
Tom Kent wrote:
So, I tried it, but surprisingly, it didn't make any difference. I'm not sure why there wasn't an error, it seems like one of HandleAccept and &HandleAccept would cause some type of error.
Also, I'm not having the problem getting through the acceptor. The server successfully gets the accept callback for the connection from the client (and the client gets its callback as well). Its the aysnc_send/async_read that doesn't ever get a callback. I tried using the reference to HandleAccept in those as well, but like I said above, saw the *exact* same results.
Tom
IIRC, an io_service object is not permitted to make copies of arguments supplied to initiating functions outside its own thread. In your example, you initiate an asynchronous operation from thread A (async_accept), and io_service runs in thread B (io_service.run()). At least, that's if I understood http://tinyurl.com/yhw95xj correctly, the section about whether or not Asio is allowed to make copies of your supplied arguments. Cheers, Rutger
Tom Kent wrote:
So, I tried it, but surprisingly, it didn't make any difference. I'm not sure why there wasn't an error, it seems like one of HandleAccept and &HandleAccept would cause some type of error.
Also, I'm not having the problem getting through the acceptor. The server successfully gets the accept callback for the connection from the client (and the client gets its callback as well). Its the aysnc_send/async_read that doesn't ever get a callback. I tried using the reference to HandleAccept in those as well, but like I said above, saw the *exact* same results.
Tom
As Igor suggested, the io_service running your client runs out of work after connecting. In addition, you should replace gotTransfer_; by gotTransfer_ = true; Cheers, Rutger
participants (3)
-
Igor R -
Rutger ter Borg -
Tom Kent