ebxml-msg message

Subject: RE: Message Pipe Confusion

From: Jacques Durand <JDurand@us.fujitsu.com>
To: "'Ric Emery'" <remery@cyclonecommerce.com>, Hamid Ben Malek <HMalek@us.fujitsu.com>
Date: Wed, 22 Mar 2006 19:50:49 -0800

Title: RE: Message Pipe Confusion

Ric:

Trying to make it shorter than Hamid's response ;-)

>So, how can an error message be assigned to a pipe, if the spec
> specifically says that signals (which errors are a type of signal) cannot > be assigned to a pipe?

Editorial inconsistency: should have been removed. Signals are no longer assigned to pipes as they could in earlier versions (that appeared to not be necessary, and caused more issues than it resolved, e.g. a PullRequest signal could not itself be pulled.)

> Also, I am confused about Signals not being assigned to a pipe. Do signals
> go back on the default pipe?

Pipes are just a way to partition the flow of user messages (not signal messages). Also a way to control which messages will be pulled first, and this again only concerns user messages. Absence of @pipe in a user message is associated with using the "default pipe" as it was more convenient to consider that a user message is always using a pipe.

Jacques