How are typical iBus applications structured?
A typical iBus application uses one of the asynchronous communication models (publish/subscriber or point-to-point). The distributed application is driven by the producer(s) generating messages, very much like modern graphical user interface based local applications. An older legacy code that is being retro-fitted into a more decoupled environment may benefit from using the blocking, synchronous interaction model provided by iBus as well.
