OASIS ebXML Messaging Services TC

 View Only
  • 1.  Groups - Multi-hop Section Draft 0.6 (ebMS3-Multihop V06.doc) uploaded

    Posted 07-15-2008 07:10
    The document revision named Multi-hop Section Draft 0.6 (ebMS3-Multihop
    V06.doc) has been submitted by Mr. Sander Fieten to the OASIS ebXML
    Messaging Services TC document repository.  This document is revision #4 of
    ebMS3-Multihop.doc.
    
    Document Description:
    Draft of the multi-hop section.
    V0.3:
    - a few updates in the definition section (editorial)
    - added a commented Flow diagram (section 1.7.1) on RM sequence
    establishment. To review.
    V0.4:
    - section 1.5 (Intermediary Role) rewritten, though not complete yet.
    (diff with 0.3 visible)
    V0,5:
    - section 1.5 updated based on feedback and extended for response
    messages.
    V0.6:
    - Added text to section 1.5 on streaming and store-and-forward models for
    implementing intermediaries 
    
    View Document Details:
    http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/document.php?document_id=28861
    
    Download Document:  
    http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/28861/ebMS3-Multihop%20V06.doc
    
    Revision:
    This document is revision #4 of ebMS3-Multihop.doc.  The document details
    page referenced above will show the complete revision history.
    
    
    PLEASE NOTE:  If the above links do not work for you, your email application
    may be breaking the link into two pieces.  You may be able to copy and paste
    the entire link address into the address field of your web browser.
    
    -OASIS Open Administration
    


  • 2.  RE: [ebxml-msg] Groups - Multi-hop Section Draft 0.6 (ebMS3-Multihop V06.doc) uploaded

    Posted 07-15-2008 09:36
    Sander,
    
    	reading your streaming description do 2 sub cases exist?  1) As
    you state where the ack is only sent from the intermediary to the
    originator when it receives it from the next point (full sync).  2) As
    soon as the intermediary receives the end of the message from the
    originator it sends the ack back. - i.e. small buffering and not fully
    synchronous.  I know we discussed some of these on the call but we may
    need to state these as possible implementation issues so that it is not
    a normative part of the spec but vendor options/optimisations.
    
    Regards,
    
    Ian
    
    


  • 3.  RE: [ebxml-msg] Groups - Multi-hop Section Draft 0.6 (ebMS3-Multihop V06.doc) uploaded

    Posted 07-15-2008 20:12
    Yes I think one streaming subcase (probably the most expected !) is
    missing from Sander's:
    The only difference with his case seems to be as you said the Ack is
    sent to original sender as soon as the reception is complete at
    intermediary level. So that is still async case, as far as the HTTP
    connections are concerned .  
    
    -Jacques