Re: T2 Clarify TimeToLive

[Martin W Sachs <mwsachs@us.ibm.com>]

persistDuration is one of those reliable-messaging parameters (section
10.2) whose source isn't defined in the MS spec. It isn't clear to me that
it is in the message header since 10.2.8 doesn't say so.  In any case,
since it is in the CPA, it should come from the CPA (or the static data
that is there when there isn't a CPA).  Since it is a static parameter, it
isn't needed in the message header.

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
*************************************************************************************



Dan Weinreb <dlw@exceloncorp.com> on 09/14/2001 12:30:34 AM

Please respond to Dan Weinreb <dlw@exceloncorp.com>

To:   david.burdett@commerceone.com
cc:   ebxml-msg@lists.oasis-open.org
Subject:  Re: T2 Clarify TimeToLive



   Date: Thu, 13 Sep 2001 14:32:43 -0700
   From: "Burdett, David" <david.burdett@commerceone.com>

   Dan you said below ...

   >>>persistDuration has to be interpreted as an agreement between the two
   parties that every (reliable) message will have a TTL <= persistDuration
<<<

Excuse me, I just realized that I have been confusing the
persistDuration element of the CPA with the persistDuration element of
the Message.  I hadn't realized that both existed.  How do the two
interrelate?  Is the CPA value some kind of constraint on the value
in a message?

   Currently persistDuration is a value that is set by the MSH that
receives
   the message.

I'm sorry, I'm not understanding this.  If we're talking about the
persistDuration in the CPA, then it's not set by one MSH; rather it's
pre-agreed by both sides.  If we're talking about the persistDuration
field in the message, I guess I don't understand how it can be set by
the MSH that receives the message.  Surely the MSH that sends the
message is the one that writes all the header elements and values, and
the MSH that receives the message simply reads them.  I think I must
be misunderstanding something...

-- Dan


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>