OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ebxml-msg] Node type definitions


I assume that in you're definition you're talking about receipt of data 
/ messages on the transport level, i.e. the http connection? So in the 
store and forwatd/collect case the message is only forwarded or made 
available when it is completely received by the intermediary. And in the 
streaming case data received is forwarded immediately after the 
intermediairy has made a routing decision.


ian.c.jones@bt.com wrote:
> All,
>         my starter definitions for the types of node from Sander's 
> proposal, feel free to add/refine and argue:
> Definitions of node types
> *Store and forward*
> The node completes receipt of the transmission before beginning 
> transmission to the next mode. i.e 2 separate sequential processes 
> that the second does not start before successful completion of the first.
> *Store and collect*
> The node completes receipt of the transmission before allowing it to 
> be retrieved (pulled). i.e. 2 separate process that the second cannot 
> be attempted until the first is complete but the second process is 
> always initiated by the other party.
> *Streaming*
> The node passes information as soon as it is received.  i.e. it just 
> routes data to the next node as soon as possible it does not store any 
> data.
> Ian Jones
> Chair OASIS ebXML Messaging Services TC
> Email: ian.c.jones@bt.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]