In the Cascades environment touch events are passed as SIGNALS which are received by SLOTS. This message passing implementation is bound to the threading model and does not have a direct inter process counterpart. Theoretically you could implement something on top of the QNX message passing system, or on top of BlackBerry Platform Services (BPS). This might be necessary if you need the kind of performance available within a single application.
The other option is to use the invokation API that BlackBerry provides in Cascades. This is a very flexible inter-process communications protocol but is inherently synchronous. Normally UI focus moves from the invoking process to the invoked process, this does not sound like what you want. The invoked process can return immediately after receiving the invokation and before posting any UI elements, but there is still the overhead of launching the invoked process, at least in the first instance, and context switching in other instances.
It might be more fruitful to be more specific about what you are really trying to accomplish.