boost-asio

boost library version 1.53 Debian Linux 6.0 ( Linux 2.6.32-5-amd64 on x86_64 ) It is hard to test own software when valgrind log contains lots of warnings. So with no changes I built the HTTP server3 example and run it under the Valgrind. Take a look, please. Did I miss something? valgrind --tool=helgrind --log-file=valgrind.log ./server3 0.0.0.0 83 5 /root/server3 Here is the Helgrind log (edited to 30000 body characters limit, full log http://pastebin.com/Vkbr9vsA ): Helgrind, a thread error detector Copyright (C) 2007-2012, and GNU GPL'd, by OpenWorks LLP et al. Using Valgrind-3.9.0.SVN and

I have a Boost ASIO-based C++ server program and I'd like to be able to set the source IP address used by TCP to that of another server. I know one can read the source and destination IP addresses but presumably they can be set as well? Presumably if I set the "wrong" source IP address in the C++ code there will be some interaction with the network stack. Won't the network stack re-set the source IP address on the way out even if the C++ code is right? Is the right way to do this to write C++ ASIO code to pick a specific virtual network interface? One that is configured with the "wrong" static

I have a thread pool with boost::io_service on top. I use it for different CPU-bound tasks in whole application. For some tasks, I have to guarantee that tasks will be executed in specified order (decoding video stream). Using io_service::strand guaranties that tasks will not be executed currently, but it has no guarantee about the order of execution. In other words, task #5 may be executed before task #4. Is there any method to solve that problem, other than scheduling next task after executing of current. strand provides both the guarantee of not executing completion handlers concurrently

My question How do I avoid a data race when using two threads to send and receive over an asio::ip::tcp::iostream ? Design I am writing a program that uses an asio::ip::tcp::iostream for input and output. The program accepts commands from the (remote) user over port 5555 and sends messages over that same TCP connection to the user. Because these events (commands received from the user or messages sent to the user) occur asynchronously, I have separate transmit and receive threads. In this toy version, the commands are "one", "two" and "quit". Of course "quit" quits the program. The other

I am currently trying to transfer some JSON data over the network from a client to a server using the socket API of boost-asio. My client essentially does this: int from = 1, to = 2; boost::asio::streambuf buf; ostream str(&buf); str << "{" << "\"purpose\" : \"request\"" << "," << endl << "\"from\" : " << from << "," << endl << "\"to\" : " << to << "," << endl << "}" << endl; // Start an asynchronous operation to send the message. boost::asio::async_write(socket_, buf, boost::bind(&client::handle_write, this, _1)); On the server side I have the choice between various boost::asio::async_read*

I am looking to use boost::asio to read from a 12 digit keypad. I currently can do it without boost, this way: fd = open ("/dev/input/event0", 0_NONBLOCK); read (fd, &ev, sizeof ev); Do you know how I could do this with boost::asio? I am using Linux and c++. This post and this post are useful. I would not use serial port port (io, "/dev/usb/hiddev0") because its not serial, right? Thank you. On my system, event2 represents the mouse, and the following simple readloop program works like a charm. Run as root : #include <boost/asio.hpp> #include <boost/asio/posix/stream_descriptor.hpp> #include