broadcast keyword
This ia an construct used inside a route based on enterprise integration patterns
. It routes the same message to more than one service in parallel.
It is used within the flow definition of a "route" and currently must be the final statement in a route definition
Syntax
...
broadcast do
route to "endpoint x" # occurs two or more times
end
...
Nesting
each "route" inside the broadcast receives the same message in parallel. A route keyword is used to allow for further nesting of statements.
The route inside the broadcast can be a code block to define a nested flow.
broadcast do
route do
to "filterInBranch1" # filter
to "branch1endpoint" # final provider endoint
end
route do
to "filterInBranch2" # filter
to "branch2endpoint" # final provider endoint
end
end
in effect statements can be nested recursively inside code blocks.
IFL enhancements to consider
- What would it mean to allow for further instructions after a "broadcast"? Would it pipe the input that did flow into the broadcast to the following instruction, sequentially after the broadcast completed?
- Should we add an aggregate keyword to join multiple responses before continuing?
- What other enterprise integration patterns constructs should make it into the language?
This page (revision-3) was last changed on
06-Oct-08 13:33 PM, -0700
by Louis Polycarpou.
This page was created on
04-May-08 17:26 PM, -0700 by AndiEgloff.
More info...