[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Comment on the TRP overview and Requirements documents
>>> A full specification of the ack responsibilities/assumptions of both sides is very important.<<< I agreee. >>>Words are nice, state diagrams are better.<<< I also agree and would expect these to be covered in the specs we need to produce on document exchange templates and reliable messaging. David -----Original Message----- From: Peter D. Pruyne [mailto:pdp@mcs.net] Sent: Tuesday, March 07, 2000 9:54 PM To: ebXML-Transport@lists. oasis-open. org Subject: Re: Comment on the TRP overview and Requirements documents > 2. Message 4.2 1(b) states "failure to deliver a document should be > notified to the party that sent the document" > > I agree, however, in the case where the document could not be parsed > (specifically the return address in the header) is this possible? > > Maybe the methodoloy should be that a message that is not acknowledged > should be considered not delivered. The use models for business may be > stricter than that with email, http etc. > A full specification of the ack responsibilities/assumptions of both sides is very important. Words are nice, state diagrams are better. PDP
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC