Andrew, > Create a new function messaging_client_init() which can be used when > we don't have a server messaging context. We should replace the > datagram messages with stream sockets in this case, so we don't have > to create a unique socket.
I still don't quite understand what you're getting at here. How would using a stream socket instead of a datagram socket avoid the socket creation? All stream versus datagram does is determine: 1) whether the OS provides the message boundaries, or we provide them ourselves 2) whether we have to do connect/accept calls In both ways, SOCK_STREAM sockets are more complex (and slower) to deal with. I just can't see any advantages for our messaging code unless perhaps we want to send very large (multi MB) messages. Cheers, Tridge