[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Action item on: how errors generated by an Intermediary can be pulled
The intermediary MUST then respond to a PullRequest authorized for the error MPC, with an intermediary error message. If no error message is posted on the error MPC, a single EmptyMessagePartitionChannel eb:Error will be returned as response to a pull request.
A chain of intermediaries MAY be configured to route intermediary error messages over a multi-hop path, as described in Section 2.5.2.2, Multihop One-Way , case 3b. In such a configuration, the PullRequest signal may be sent by another intermediary, that will in turn post the received intermediary error message on its local error MPC (with same identifier) waiting for it to be pulled again, acting as a Sender for this error message, as described in the "Pull-on-Pull" forwarding pattern (section 2.6.3). Such a multi-hop path for pulling errors, may also reach an end-point MSH and be used to carry errors generated by this end-point. In such a case, the end-point MUST comply with above rules and only use this MPC for posting error messages.
-jacques
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]