IMHO, a RMI C++ package should be independent of the underlying transport protocol. This last one couldbe abstracted as an iostream like the fstream classes for tcp/udp, one could use a socketstream (SocketC++ or others as starting point) for x25, one could use x25stream for pipe/named pipe, one could use pstream (@sourceforge) for file, one could use fstream and so on templates are good for this kind of job FA -- A good friend will come bail you out of jail.......... but, a true friend....will be sitting next to you saying: "...that was fun." "Matt Hurd" <matt.hurd@gmail.com> a écrit dans le message de news:8f48d4a04083123442a8464a4@mail.gmail.com...
Francis ANDRE <francis.andre@easynet.fr> wrote:
Now that the serialization library is part of boost, could this be a item to add the the wishlist at boost.org???
tcp/udp wrapping should probably come first.
matt. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost