MHonArc v2.5.0b2 -->
ebxml-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [ebxml-msg-comment] Public Comment
Gait,
Thanks for the comments. I've cc:d the main list so others can
comment here.
The one item I'm familiar with is the "stage delivery" support for
push/pull.
I agree that you can do this today with v2 - but its not directly
supported - so implementations are not consistent. Therefore the
need is to provide a formal mechanism in v3 here.
Again - application practice has shown we do need this - particularly
for large payloads - or to avoid peak surges overwhleming central
systems - so non-time-critical deliveries can be picked up at times
when the receiver has slack capacity. As you note it does require
longer message persistence by the sender - but again - this can be an
essential part of the process - e.g. the sender has fulfilled legal
requirement to submit by a deadline - and locked their submission
package - but the actual payload delivery can be deferred.
Clearly you have to have agreement on the CPA for the staged delivery
responsibilities and timings. I believe there is
enough parameters here to accomplish those settings between two
partners so timings and delivery responsiblity is not an
issue. As always - probably some example would help clarify the
exact details.
That is just one use case from my experience - I know others have
more too.
Anyway - the bottom line is that real world applications have shown
us the need to have support in v3 for this formal push/pull
mechanism.
Hope that is enough clarification on the
rationale behind it.
Thanks, DW