On Jan 18, 2007, at 1:23 AM, Andre Merzky wrote:
|Unreliable|: \> messages MAY (or may not) reach the remote clients.\\[0.3em] |Atomic|: \> |Unreliable|, but a message received by one client is\\ \> guaranteed to (MUST) arrive at all clients.\\[0.3em] |SemiReliable|: \> messages are guaranteed to (MUST) arrive at all\\ \> clients, but may arrive more than once.\\ [0.3em] |Reliable|: \> all messages are guaranteed to (MUST) arrive at\\ \> all clients.\\[0.3em] \end{tabbing}
That is similar to your list, but adds the 'atomic' one. Not sure if that is useful (sounds like) or easily implementable (??), but I found it in a list of relibility modes for message transmissions which looked sensible, and seems to be close to what you propose.
That sounds good to me.
Got you (I think) :-) Yes, that makes sense. I added a 'topology' enum and attribute, which is handled similarly to the 'reliability' property (static over connection/endpoint lifetime, inspection via ReadOnly attribute).
New draft is attached, with new sections marked. It would be great if you could review the paragraphs about connection topology.
Looks good to me! I think you have addressed all of my concerns. -john