[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Messaging Service Comment
Again, sorry about the deadline. This comment belongs on the work list, not as a correction to the current version. Some of the dicussions about interrelations between Reliable Messaging and transport protocols point up the need to state the assumptions about the transport function in some manner. One possibility is some kind of definition of a conceptual interface between the Messaging Service and the transport function. It's fine to say that the messaging service is agnostic to the transport protocol but in real life, the Messaging Service run-time must interact with the transport run-time. Design of the messaging service protocol must be with the understanding of what goes on in the most likely transports. Since it is highly likely that an implementation will include both the messaging service and the transport function, it may be sufficient to express the interactions as a series of informative notes (or an informative appendix) rather than as a formal interface definition. The important point is that the assumptions have to be stated to ensure that the messaging service and transport function will work together correctly. Regards, Marty ************************************************************************************* Martin W. Sachs IBM T. J. Watson Research Center P. O. B. 704 Yorktown Hts, NY 10598 914-784-7287; IBM tie line 863-7287 Notes address: Martin W Sachs/Watson/IBM Internet address: mwsachs @ us.ibm.com *************************************************************************************
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC