boost-asio

问题 Is it possible to call async_wait several times on the same boost::asio::deadline_timer? What I mean to do is something like the following: t->expires_from_now(delay); t->async_wait(f1); t->async_wait(f2); Does this ensures that the two functions will be called? Does this ensures that the two functions will be called in this order? If not, any idea how to have f1 and f2 successively called when the timer times out? (I don't care if another handler is executed between the calls to f1 and f2).

问题 I'm in the process of constructing a Socket class that uses boost::asio . To start with, I made a connect method that took a host and a port and resolved it to an IP address. This worked well, so I decided to look in to async_resolve . However, my callback always gets an error code of 995 (using the same destination host/port as when it worked synchronously). code : Function that starts the resolution: // resolve a host asynchronously template<typename ResolveHandler> void resolveHost(const

问题 I'm in the process of constructing a Socket class that uses boost::asio . To start with, I made a connect method that took a host and a port and resolved it to an IP address. This worked well, so I decided to look in to async_resolve . However, my callback always gets an error code of 995 (using the same destination host/port as when it worked synchronously). code : Function that starts the resolution: // resolve a host asynchronously template<typename ResolveHandler> void resolveHost(const

问题 I'm reading from a boost::asio::ip::udp::socket like this: using boost::asio::ip::udp; // ... char recv_buf[128]; udp::endpoint sender_endpoint; size_t len = socket.receive_from(boost::asio::buffer(recv_buf), sender_endpoint); Now, this works perfectly fine, but the maximum amount of characters that I am able to recieve is now 127. However I am facing a problem because I need to accept some data input of which the length can greatly vary (and is not of well-defined length with prefixed

问题 I'm developing a peer-to-peer communications network for use over a LAN in an industrial environment. Some messages are are just asynchronous, and don't require a response. Others are request-response. The request messages (and the async messages) are sent to a multicast group, and the replies to requests are sent unicast. Each endpoint, therefore, receives UDP packets that are sent to the multicast group, and also receives messages that are just sent to it using plain unicast. So far it's

问题 I wrote a proxy service program that used boost asio, the proxy server has two socket(client_socket_,server_socket_)，If one of the socket is disconnected another one to remain active。For example, if read from client_socket_ results in error, i will close client_socket_ and then wait for client to reconnect and after client reconnects, I read from one socket and write to another. The problem is that, when i close the client_socket_ how to cancel the asynchronous operation in server_socket_? if

问题 Upgraded Ubuntu today from 14.10 to 15.04. Now seeing different behaviour either in boost::asio::async_read() , boost::asio::posix::stream_descriptor , or tap/tun interfaces. Calling async_read() immediately returns boost::asio::error::eof . If I ignore the error and loop back up to start a new async_read() it does eventually read when bytes are available, and the application continues to work. The problem with doing this workaround loop is the application now consumes 100% of a core as it

问题 I have 2 cases: Client connects, send no bytes and wait for server response. Client connects, send more than 1 bytes and wait for server response. Problem is next: in 1st case I should read no bytes and get some server response. in 2nd case I should read at least 1 byte and only then I'll get a server response. If i try to read at least 0 bytes, like this: async_read(sock, boost::asio::buffer(data), boost::asio::transfer_at_least(0), boost::bind(&server::read, this, boost::asio::placeholders:

问题 I have 2 cases: Client connects, send no bytes and wait for server response. Client connects, send more than 1 bytes and wait for server response. Problem is next: in 1st case I should read no bytes and get some server response. in 2nd case I should read at least 1 byte and only then I'll get a server response. If i try to read at least 0 bytes, like this: async_read(sock, boost::asio::buffer(data), boost::asio::transfer_at_least(0), boost::bind(&server::read, this, boost::asio::placeholders:

问题 I understood that calling boost::asio::ip::tcp::socket::async_receive (or boost::asio::ip::tcp::socket::async_send ) two times may result in a bad behavior.. Is it OK if i call boost::asio::ip::tcp::socket::async_recive and boost::asio::ip::tcp::socket::async_send at the same time? I am going to have 2 or more threads running the boost::asio::run so you need to take that into account.. Thanks 回答1: This has to be OK. How else would you perform full duplex async communications on a single