12 Replies Latest reply on Jan 18, 2006 5:47 AM by marklittle

one bus for synchronous and asynchronous communication ?

tom.baeyens Jul 28, 2005 4:55 PM

from the wiki, i read that the new microcontainer is based on the same principles as the JMX microkernel. which means synchronous (same thread) decoupled invocations.

i wonder if we can create one bus that supports synchronous invocations (jmx-style) as well as asynchronous invocations (jbi-style).

i tried this out with a small doodle and i think this could work.

anyone an opinion on this ?

regards, tom.

1. Re: one bus for synchronous and asynchronous communication ?

juha Jul 28, 2005 5:00 PM (in response to tom.baeyens)

You mean JMX microkernel ;-)
Actions
2. Re: one bus for synchronous and asynchronous communication ?

tom.baeyens Jul 28, 2005 5:03 PM (in response to tom.baeyens)

that's what i said :-)

regards, tom.
Actions
3. Re: one bus for synchronous and asynchronous communication ?

arvinder Aug 4, 2005 10:13 AM (in response to tom.baeyens)

You would need multiple bus abstractions, think multiple channels, some for control, some for event, some domain specific etc.
Actions
4. Re: one bus for synchronous and asynchronous communication ?

tom.baeyens Aug 4, 2005 10:15 AM (in response to tom.baeyens)

could you elaborate ? i don't your point yet.

regards, tom.
Actions
5. Re: one bus for synchronous and asynchronous communication ?

arvinder Aug 4, 2005 10:23 AM (in response to tom.baeyens)

Hi

In terms of the message channels/bus within the integration environment, for a given bus you could specify the way a message is handled, say through meta information contained in the request to specifiy invocation type, e.g request-response or request only aka fire and forget. This is similar to what the spec has defined interms of the normalized message exchange.

So within the integation environment, you have several service engines/binding components that could listen in on a specific channel, say a control channel, that is used to send control based messages to these components. At this point you also make the service/engine and binding components use an event channel to send ... events to interested parties etc.

This is what i was referring to about different channels etc.
Actions
6. Re: one bus for synchronous and asynchronous communication ?

tom.baeyens Aug 4, 2005 10:26 AM (in response to tom.baeyens)

ok thanks.

regards, tom.
Actions
7. Re: one bus for synchronous and asynchronous communication ?

kryptontri Sep 6, 2005 3:56 PM (in response to tom.baeyens)

Is this module/project dead or just in stasis ? There seemed to be a lengthy discussion going on earlier ,.. but now seems very quiet ?
Actions
8. Re: one bus for synchronous and asynchronous communication ?

starksm64 Sep 6, 2005 3:59 PM (in response to tom.baeyens)

Its in deep thought.
Actions
9. Re: one bus for synchronous and asynchronous communication ?

ovidiu.feodorov Sep 6, 2005 5:38 PM (in response to tom.baeyens)

Sort of ...

Hopefully it will became a little more shallow ... and visible ... the second half of Sep. Stay tuned.
Actions
10. Re: one bus for synchronous and asynchronous communication ?

kukeltje Sep 7, 2005 2:45 PM (in response to tom.baeyens)

42
Actions
11. Re: one bus for synchronous and asynchronous communication ?

kryptontri Jan 13, 2006 10:07 AM (in response to tom.baeyens)

Still in deep thought ?
Actions
12. Re: one bus for synchronous and asynchronous communication ?

marklittle Jan 18, 2006 5:47 AM (in response to tom.baeyens)

Stay tuned, but don't expect much activity until the end of the month.

Mark.
Actions

Go to original post