RE: T2, Proposed solution for ... Re: SyncReply andReliableMessagingMethod in QualityOfServiceInfo

[David Fischer <david@drummondgroup.com>]

We have discussed this in the past and I have asserted that garbage collection
would actually never happen at the To Party (unless it was some sort of IM such
as a Mailroom).  For legal reasons, garbage collection of business documents
cannot occur until after 7 years (garbage collection is not in the spec is it?).
Instead of garbage collection, the To Party might occasionally Archive, which
almost amounts to the same thing.  Even this would be infrequent.

I suppose such a restriction would have something to do with either
PersistDuration, TimeToLive or n*Retries*RetryInterval.  Or maybe this is
something new which should go in the CPA?  I would lean toward PersistDuration
but I am not sure we have a definitive understanding of what this should be.
OTOH, this question might be out of scope.

Ralph works for an EDI software company, how often is archiving typically done?
Is it done?

Regards,

David Fischer
Drummond Group.

-----Original Message-----
From: Dan Weinreb [mailto:dlw@exceloncorp.com]
Sent: Wednesday, September 19, 2001 10:25 PM
To: david@drummondgroup.com
Cc: arvola@tibco.com; ebxml-msg@lists.oasis-open.org
Subject: Re: T2, Proposed solution for ... Re: SyncReply and
ReliableMessagingMethod in QualityOfServiceInfo


   Date: Wed, 19 Sep 2001 21:30:37 -0500
   From: David Fischer <david@drummondgroup.com>


							The From Party can perform
   a Retry at any time it deems appropriate.

Well, actually, I think there has to be some kind of restriction or
else the To Party would never be able to garbage-collect its set of
already-received message ID's, as we've discussed in the past.