Message Routing Paradigms

[Jani Launonen]

>I am aware of Erlang's messaging capabilities and yet there is still a
>general need for higher level protocols like the one's I mentioned.
>
>Even the CosEvent module demonstrates acceptance of the decoupled
>publish/subscribe paradigm.

You might want to check out CosNotification instead of CosEvent. It gives
the same functionality plus a whole lot more.

>Do you or anyone else have any idea of messaging "middleware" developed
>with Erlang for Erlang that addresses message routing like the CosEvent
>module, but without the overhead of CORBA?

If your Orbers are configured to be on the same Orber domain
(http://erlang.stacken.kth.se/doc/r9b/lib/orber-3.3/doc/html/ch_install.html)
they use the Erlang's distribution protocol to communicate with each other
bypassing IIOP's overhead. They (in side one Orber domain) can communicate
with other ORB's and other Orber domains with IIOP, of course.

Cheers,

Jani

>Sincerely,
>Eric
>
>
>
>-----Original Message-----
>From: owner-erlang-questions@REDACTED
>[mailto:owner-erlang-questions@REDACTED] On Behalf Of Sean Hinde
>Sent: Friday, December 13, 2002 4:31 AM
>To: 'Eric Newhuis'; erlang-questions@REDACTED
>Subject: RE: Message Routing Paradigms
>
>
>Eric,
>
>I'm not sure there is really a need for a paradigm - it is the basis of
>Erlang.
>
>To get 10k per second you are probably not wanting to do a lot of
>processing on each message - but a simple round robin load balancer
>based on differently tagged messages is probably no more than a single
>gen_server with a little logic
>
>I'm not familiar with these different mechanisms but my guess is that
>they are only needed because they don't have Erlang :-)
>
>Sean
>
>-----Original Message-----
>From: Eric Newhuis [mailto:enewhuis@REDACTED]
>Sent: 13 December 2002 04:07
>To: erlang-questions@REDACTED
>Subject: Message Routing Paradigms
>
>
>To whomever knows,
>
>Are there any good information sources regarding Erlang message routing
>paradigms?
>
>I am interested in decoupling publishers and subscribers, possible
>space-based load-balancing (like Java Spaces or IBM T-spaces),
>content-based subject routing, and it must handle on order of 10K
>messages per second per 1GHz CPU.
>
>
>Sincerely,
>Eric Newhuis
>
>
>
>
>
>
>NOTICE AND DISCLAIMER:
>This email (including attachments) is confidential.  If you have
>received this email in error please notify the sender immediately and
>delete this email from your system without copying or disseminating it
>or placing any reliance upon its contents.  We cannot accept liability
>for any breaches of confidence arising through use of email.  Any
>opinions expressed in this email (including attachments) are those of
>the author and do not necessarily reflect our opinions.  We will not
>accept responsibility for any commitments made by our employees outside
>the scope of our business.  We do not warrant the accuracy or
>completeness of such information.
>

-+-+-+-
Jani Launonen
Student. . . . . . . . . .University of Oulu, Dept. of EE
Assistant Researcher . . .Apricot Project

"Computing is a field which has one of the shortest collective memories
of any engineering or scientific discipline." - Marty Fouts, comp.distributed