|
WebFlow components (modules) are developed independently of each other.
|
|
They can interact with each other through WebFlow events. (They can use remote invocation, but it requires the caller to have reference to the target module, which violates the WebFlow "module independence" rule).
|
|
There is only one type of WebFlow events. An event (same as a message) is a (self-describing) object that encapsulates data to be transferred from one module to another.
|
|
Each module can serve as a sink.
|
|
Event sources and sinks are associated at run time by the client invoking CORBA dynamic interfaces.
|
