Ted asks:
> What is your perspective on JavaOS's Bidirectional Events (section 3.5)?
The only thing you need to support bidirectional events is a way to
identify the event that you are responding to. That would be easily done
if the producer tags the event with a unique id prior to sending it.
Then when a consumer received it, and wanted to send a response, it would
tag the response with the original unique id.
I'ld rather not explicitly build this into the core Event Manager service
just yet (trying to keep things simple for the moment), since the basic
pub/sub event capability will allow for it for those apps that need it.
Then we can see how much a request/response (bi-di) paradigm is required
and whether it makes sense to make it a standard feature. In the
meantime, it's not that hard to do req/resp event conversations by using
two different event types, a unique id, with two embedlets that register
as both producers and consumers.
...Andrzej
Chaeron Corporation
http://www.chaeron.com
|