| Sign In/My Account | View Cart |
We've expanded our XML news coverage and improved our search! Search for all things XML across O'Reilly!
|
|
 |
Royalty-free WS-ReliableMessaging republished
David A. Chappell URL: ftp://www6.software.ibm.com/software/developer/library/ws-reliablemessaging... WS-ReliableMessaging was republished on Tuesday of this week. The most substantial change was in the legal language, which grants royalty-free rights to implement. The most important technical difference is the relaxing of a restriction that used to require that a recipient keep track of message sequences beyond the receipt of a TerminateSequence message. The recipient is now allowed to disregard any straggling messages that arrive after a sequence has been terminated. For more information -http://www-128.ibm.com/developerworks/webservices/library/ws-rmreload/ ftp://www6.software.ibm.com/software/developer/library/ws-reliablemessaging200502.pdf Dave David A. Chappell is vice president and chief technology evangelist for is vice president and chief technologist for SOA at Oracle Corporation. Showing messages 1 through 1 of 1.
Return to weblogs.oreilly.com. Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc., disclaims any and all liabililty for that content, its accuracy, and opinions it may contain.
|
|
Sponsored By: |
||||||||||||
©2009, O'Reilly Media, Inc. (707) 827-7000 / (800) 998-9938 All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. |
About O'Reilly
Academic Solutions Authors Contacts Customer Service Jobs Newsletters O'Reilly Labs Press Room Privacy Policy RSS Feeds Terms of Service User Groups Writing for O'Reilly |
More O'Reilly Sites
O'Reilly Radar Ignite Tools of Change for Publishing Digital Media Inside iPhone O'Reilly FYI makezine.com craftzine.com hackszine.com perl.com xml.com Partner Sites InsideRIA java.net O'Reilly Insights on Forbes.com |
Content Archive Business Technology Computer Technology Microsoft Mobile Network Operating System Digital Photography Programming Software Web Web Design |
The only thing that surprises me is that only one model of sequence resending seems to be supported.
The standard example message exchange (reproduced in most articles) shows how msg 2 in a 3 msg sequence is dropped and how this is then resent.
For this to be useful to the recipient it would have to implement a temporary store of incoming messages which it can use to fill in the gaps following resends.
In other protocols the recipient has the option of telling the sender that a set of messages were missing and that it would like all messages starting at the first missing message resent. In this way the recipient can be implemented without a temporary store. One example of a protocol like this is the FIX session protocol.
Do you know if these sort of models were considered?