Re: Reliability is really two-phase (was RE: Reliable Web Services)

> 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