ebxml-msg — archive

[System]

Dan You wanted a use case where where you have an IM "that's unreliable but must act at the ebXML MS level of abstrction, i.e. it understands and interprets the data formats described in the MS spec". In my last email at (http://lists.oasis-open.org/archives/ebxml-msg/200109/msg00191.html) I explained the benefits of an ebXML MSH and included the following diagram: A -------------- BM ------ B1 ------- B MSH MSH MSH APP1 | | -------- B2 ------- B | MSH APP2 | ----- Inteface ---- B App APP3 Suppose the B2 MSH and the B APP2 are running on the same server and the server suffers a head crash. In this case the BM MSH should respond with a Delivery Failure Notification to A when A sends it a reliable message. You also cannot reasonably guarantee that the B2MSH when would NEVER lose data when it crashed. Therefore it is quite possible that a Delivery Receipt could get lost. This in fact suggests a really nasty use case. Suppose: 1. The B2 MSH forwards the message to APP2 2. The B2 MSH cathes fire and as a result loses both its database and recovery log files and so CANNOT recover the fact that it previously forwarded a message to APP2. Thoughts? David