OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC