– if sending msg, need own msg markers. msg starting and ending
markers or some way to determine the beginning and the end of msg.
Say, using a length with a well-known msg header etc
– stream base reliable delivery
– mesh well with select()
– load balancing on various socket fds in 1 single thread

– a msg level set of api, don’t need to worry about start and end of msg, all the streaming and framing details are taken care of
– get the whole msg at a time, not by stream
– single thread per session so it’s slower then just tcp(?)
– many jms msg brokers available to use