Streaming model

["Sander Fieten" <sander@fieten-it.com>]

Jacques, Ian,

I did think of that specific case of streaming but didn't describe it because in this scenario there's no assurance about the transfer of the message to the next hop. I tought it would be useful to at least have some assurance about the message tranfers, although this scenario reduces the bandwidth problem as teh Receive operation ends before the Send does. 

I'll rewrite the text on the streaming model and adapt the sequence diagram to describe this scenario. The scenario already in the document can than be described as an alternative implementation with (little) more guarantees and a remark on synchronous transfers.

Sander


----- originele bericht --------

Onderwerp: RE: [ebxml-msg] Groups - Multi-hop Section Draft 0.6 (ebMS3-Multihop V06.doc) uploaded
Verzonden: di, 15. jul 2008
Van: Durand, Jacques R.<JDurand@us.fujitsu.com>

> 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
> 
> -----Original Message-----
> From: ian.c.jones@bt.com [mailto:ian.c.jones@bt.com] 
> Sent: Tuesday, July 15, 2008 2:36 AM
> To: ebxml-msg@lists.oasis-open.org
> Subject: RE: [ebxml-msg] Groups - Multi-hop Section Draft 0.6
> (ebMS3-Multihop V06.doc) uploaded
> 
> 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
> 
> -----Original Message-----
> From: sander@fieten-it.com [mailto:sander@fieten-it.com]
> Sent: 15 July 2008 08:10
> To: ebxml-msg@lists.oasis-open.org
> Subject: [ebxml-msg] Groups - Multi-hop Section Draft 0.6
> (ebMS3-Multihop V06.doc) uploaded
> 
> 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?docu
> ment_id=28861
> 
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/download.php/2886
> 1/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
> 
> ---------------------------------------------------------------------
> 
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 

--- originele bericht einde ----