29 Dec
2004
29 Dec
'04
7:02 p.m.
----- Original Message ----- From: "Jody Hagins" <jody-boost-011304@atdesk.com> To: <boost@lists.boost.org> Sent: Wednesday, December 29, 2004 6:27 PM Subject: Re: [boost] Re: Serialization and async messaging <snip>
I could be missing the boat, but this is the usual problem with serialization methods, when using them with sockets. For this to work, the operator>>() has to know that there is no more data (i.e., correctly interpret return code of read when the fd is in non-blocking mode), and keep its current state so that the next call to operator>>() will continue where the last call left off.
That is indeed what I have been trying to say :-)