- Boost-users - lists.boost.org

[BoostCon 2010] Submission deadline extended
by Hartmut Kaiser 11 Dec '09

11 Dec '09

In 2010 BoostCon celebrates its 4th anniversary in Aspen. You are invited to submit a paper or a session (see the original call for participation here: http://www.boostcon.com/community/wiki/show/Start/) for BoostCon 2010, Aspen on May 10 - May 14th, 2010. Please, see http://www.boostcon.com for more information. Important dates: Proposal submissions Extended to January 3, 2010 Proposals decisions sent January 25, 2010 (tentative program available) Fully scheduled program available February 10, 2010 Session materials due April 15, 2010 Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) David Abrahams, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

Re: [Boost-users] Simple serial port demonstration with boost asio asynchronous I/O
by philipp_muenzel＠web.de 11 Dec '09

11 Dec '09

Hello, in reply to this old posting: http://lists.boost.org/boost-users/2008/10/41140.php I would like to kindly ask the author Jeff Gray if he tested his example on a Mac. On Linux, the example works flawlessly and lets me communicate with both "native" serial port hardware and USB-to-serial converted hardware with FTDI chips, which can be adressed via /dev/ttyUSB. On a Power Mac with OS Tiger, using boost 1.40 and the gcc 4.0 compiler, everytime I start the example I get the following errors: $ ./minicom.app/Contents/MacOS/minicom 57600 /dev/cu.usbserial-4B11 Error: Operation not supported Press Enter to exit Error: Bad file descriptor Press Enter to exit However, I can talk to the serial-via-usb hardware using some native socket functions, so the file descriptor itself can't be the problem. How can I get the minicom example to work on Mac also? Regards, Philipp ___________________________________________________________ Preisknaller: WEB.DE DSL Flatrate für nur 16,99 Euro/mtl.! http://produkte.web.de/go/02/

1 0

Workaround for g++ problem compiling Boost.Asio examples on Ubuntu 8.04.3
by David Featherstone 11 Dec '09

11 Dec '09

I'm running Ubuntu 8.04.3 as a VMware virtual machine hosted by Windows XP on a Lenovo T61 laptop. Synaptic Package Manager [or apt-get] on Ubuntu 8.04.3 offers both the libboost-dev v1.34.1 and the libasio-dev v0.3.8 packages with pre-built libraries. Version 1.34 of Boost does not have an integrated asio library; asio integration appears in v1.35 and later versions of Boost. Source code for the problematic example program can be found here: http://www.boost.org/doc/libs/1_41_0/doc/html/boost_asio/tutorial/tuttimer4… Source listing for Timer.4 The first compile problem occurs at the second #include: #include <boost/asio.hpp> The compiler cannot find this header because asio.hpp was installed under /usr/include rather than under /usr/include/boost. I fixed this issue by creating a soft link to /usr/include/asio.hpp in /usr/include/boost: $ sudo ln -s ../asio.hpp /usr/include/boost/asio.hpp Solving the second compile problem proved more difficult. The second compile problem occurred at the first use of the boost::asio namespace: printer(boost::asio::io_service& io) Changing all occurrences of 'boost::asio' to simply 'asio' solves this problem, but makes tedium of playing with the examples and developing new code that will be compatible with v1.35+ of Boost. Instead, I employed namespace declarations to (artificially) nest the asio namespace within the boost namespace. This artificial nesting is straight-forward - a single line of code: #include <iostream> #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/date_time/posix_time/posix_time.hpp> namespace boost { namespace asio { using namespace ::asio; } } class printer { public: printer(boost::asio::io_service& io) o o o Caution: I have not made exhaustive tests of this workaround, but it does compile [g++ 4.2.4] , link, and run on my platform: $ g++ -o timer timer.cpp -lboost_thread $ ./timer 0 1 2 3 4 Final count is 5 You may find more helpful information here, from the developer of the asio library: http://blog.think-async.com/ http://blog.think-async.com -- View this message in context: http://old.nabble.com/Workaround-for-g%2B%2B-problem-compiling-Boost.Asio-e… Sent from the Boost - Users mailing list archive at Nabble.com.

2 2

default mpi implementation
by Sean Farrow 11 Dec '09

11 Dec '09

Hi: Could someone give me a url for the default mpi compiler used with boost.mpi, I believe this is mpi++ but could be wrong. Any help appreciated. Sean.

1 0

Including only the needed boost headers.
by Al Gambardella 11 Dec '09

11 Dec '09

I am currently using the tokenizer library to do some simple log file processing. I am the only person on my team currently using the boost libraries. This code I wrote was originally just a utility for myself so I was able to get away with installing boost "only" on my PC. Now others on the team want to use my utility. Is there a way I can share this code with them without forcing them to install boost on there PCs? I am only using a very very small portion of the boost library so I think it would be overkill to make everyone install boost. Can I create a DLL or library to solve this? If this helps... I am running visual studio 2005. My project is not GUI based. Thanks

4 3

Re: [Boost-users] [ASIO] Wrong usage of streambuf ?
by Imran Fanaswala 11 Dec '09

11 Dec '09

> Date: Tue, 08 Dec 2009 15:03:46 +0100 > From: Axel <axel.boost(a)laposte.net> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [ASIO] Wrong usage of streambuf ? > Message-ID: <4B1E5CC2.6040103(a)laposte.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello > > I m writing a simple client/server program. On a request the server > answers "ok\r\n". It works well. I have a problem with the client. > Using async functions, I don't manage to handle the response from the > server. Once the server sent the response, I want to read the data, > close the socket, and open a new connection to the server. > > When I don't read the data sent by the server, I manage to close the > socket and repeat the operation (close the socket, and reconnect to the > server). > When I read the data, the program seems to block. > > /* Callback to the async_write function. On any request, the server > sends "ok\r_n" */ > void Client::handle_write(boost::asio::ip::tcp::socket* socket, const > boost::system::error_code& err) > { > if(!err) > { > cout << "Read..." << endl ; > // response_ is a boost::asio::streambuf variable > boost::asio::async_read_until(*socket, response_, "\r\n", > boost::bind(&Client::handle_read, this, socket, > boost::asio::placeholders::error, > boost::asio::placeholders::bytes_transferred)) ; > } > else > { > cout << "Error when writing to host: " << err.message() << "\n" ; > } > } > > void Client::handle_read(boost::asio::ip::tcp::socket* socket, const > boost::system::error_code& err, size_t bytes_transferred) > { > cout << bytes_transferred << " bytes received. " << endl ; > > /* Dont count the 2 bytes long "\r\n" string */ > int message_size = bytes_transferred - 2 ; > > > char * response_char = new char[message_size + 1] ; > response_char[message_size] = '\0' ; > response_stream.read(response_char, message_size) ; > string result(response_char) ; > delete response_char ; > response_.consume(2) ; > > socket->close() ; > delete socket ; > connect() ; > return ; > } > > If I skip the block where I read the response_ into a string, the > program works flawlessly. If I try to read the response from the > streambuf variable, the program is blocked at the next call to > async_read_until() */ > So I guess that I m doing something wrong with the streambuf variable > named "response_", but I dont understand what. Can someone explain me > what is wrong ? > > Thanks in advance. > I am not really sure what response_stream is, but I see what you are trying to do. Consider doing the following instead: void Client::handle_read(boost::asio::ip::tcp::socket* socket, const boost::system::error_code& err, size_t bytes_transferred) { ... //Note: data, will contain the "ok\r\n".. so just do some string manip to get rid of it const char* data=boost::asio::buffer_cast<const char*>(response_.data()); response_.consume(bytes_transferred); //This is the key... ... }

1 0

sending a serialized object using message_queue
by Luciano Afranllie 11 Dec '09

11 Dec '09

Hi, I am trying to send a serialized object using message_queue but I am getting a boost::interprocess_exception::library_error in the sender side. I think the problem is me but after a lot of google I could not find a way to make it work This is the method where I am trying to send the message: int RemoteMgr::sendMsgToPeers(const IPCMsg &msg) { std::cout << "RemoteMgr::sendMsgToPeers()\n"; std::ostringstream archive_stream; boost::archive::text_oarchive archive(archive_stream); archive << msg; std::string outbound_data = archive_stream.str(); std::vector<char> outbound(outbound_data.begin(), outbound_data.end()); std::cout << "outbound_data = [" << outbound_data << "]\n"; std::cout << "size = " << outbound.size() << "\n"; // TODO: Not working yet. How to send a string with serialized data? message_queue mq_master(open_only, "master_queue"); mq_master.send(&outbound, outbound.size(), 0); } Where IPCMsg is class IPCMsg { public: IPCMsg() {} IPCMsg(const std::string &type, const std::string &payload); ~IPCMsg(); std::string getSender() { return m_sender; } std::string getType() { return m_type; } std::string getPayload() { return m_payload; } template<class Archive> void serialize(Archive & ar, const unsigned int /* file_version */) { ar & BOOST_SERIALIZATION_NVP(m_sender) & BOOST_SERIALIZATION_NVP(m_type) & BOOST_SERIALIZATION_NVP(m_payload); } private: std::string m_sender; std::string m_type; std::string m_payload; }; Receiver code is like this: unsigned int priority; std::size_t recvd_size; IPCMsg msg; std::vector<char> inbound_data(100); std::cout << "Waiting for peers" << std::endl; while (!terminate) { if (mq.try_receive(&inbound_data, inbound_data.size(), recvd_size, priority)) { std::cout << "New message received.\n"; std::string archive_data(&inbound_data[0], inbound_data.size()); std::istringstream archive_stream(archive_data); boost::archive::text_iarchive archive(archive_stream); archive >> msg; std::cout << "msg type = " << msg.getType() << "\n"; } } Hope you can help. Thanks! Luciano

1 0

[ASIO] Wrong usage of streambuf ?
by Axel 11 Dec '09

11 Dec '09

Hello I m writing a simple client/server program. On a request the server answers "ok\r\n". It works well. I have a problem with the client. Using async functions, I don't manage to handle the response from the server. Once the server sent the response, I want to read the data, close the socket, and open a new connection to the server. When I don't read the data sent by the server, I manage to close the socket and repeat the operation (close the socket, and reconnect to the server). When I read the data, the program seems to block. /* Callback to the async_write function. On any request, the server sends "ok\r_n" */ void Client::handle_write(boost::asio::ip::tcp::socket* socket, const boost::system::error_code& err) { if(!err) { cout << "Read..." << endl ; // response_ is a boost::asio::streambuf variable boost::asio::async_read_until(*socket, response_, "\r\n", boost::bind(&Client::handle_read, this, socket, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)) ; } else { cout << "Error when writing to host: " << err.message() << "\n" ; } } void Client::handle_read(boost::asio::ip::tcp::socket* socket, const boost::system::error_code& err, size_t bytes_transferred) { cout << bytes_transferred << " bytes received. " << endl ; /* Dont count the 2 bytes long "\r\n" string */ int message_size = bytes_transferred - 2 ; char * response_char = new char[message_size + 1] ; response_char[message_size] = '\0' ; response_stream.read(response_char, message_size) ; string result(response_char) ; delete response_char ; response_.consume(2) ; socket->close() ; delete socket ; connect() ; return ; } If I skip the block where I read the response_ into a string, the program works flawlessly. If I try to read the response from the streambuf variable, the program is blocked at the next call to async_read_until() */ So I guess that I m doing something wrong with the streambuf variable named "response_", but I dont understand what. Can someone explain me what is wrong ? Thanks in advance.

5 8

[LibrariesUnderConstruction] Please update Boost.Coroutines entry
by Nat Goodspeed 11 Dec '09

11 Dec '09

Links: Boost Vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-… Last upload: 2009 Dec 01 Thank you!

2 2

ASIO: udp datagrams question
by Jay Sprenkle 10 Dec '09

10 Dec '09

When using asio with an async udp connection can I assume I will always receive a complete datagram or nothing at all? If packets are lost I will get nothing. If I get a data read callback I can assume the entire datagram has been received and assembled (even if it consisted of multiple packets)? Some of the underlying assumptions aren't clear from the documentation. Thanks! -- Cause united breaks guitars http://www.youtube.com/watch?v=5YGc4zOqozo

1 0