- From: Walden Mathews <waldenm@optonline.net>
- Date: Mon, 23 Dec 2002 19:36:34 -0500
- To: Assaf Arkin <arkin@intalio.com>, Mark Potts <mark.potts@talkingblocks.com>, Peter Furniss <peter.furniss@choreology.com>, "Patil, Sanjaykumar" <sanjay.patil@iona.com>
- Cc: Www-Ws-Arch <www-ws-arch@w3.org>
> There's an important principle here: you reduce the cost of development and > improve reliability if you simplify the application by putting the > complexity in separate layers. So for an RM (RM=MOM) you would automatically > do the resend without bothering the application. How many times would you resend? How long would you wait between resends? What would you tell your application while this process is going on? Would you pend your application during this process? What if your application can't afford to be pended awaiting "reliability"? What happens when an application uses an RM framework in order to reduce its complexity, observes and interprets the signs from the RM indicating that messaging was reliable, then discovers that the peer application at the other end is in some unexpected state despite assertions of "reliability"? Is this impossible? Thanks, Walden Mathews
Received on Monday, 23 December 2002 20:26:46 UTC