in reply to Instant Messaging Protocol

I would try with Spread Toolkit:

Spread is a toolkit that provides a high performance messaging service that is resilient to faults across external or internal networks. Spread functions as a unified message bus for distributed applications, and provides highly tuned application-level multicast and group communication support. Spread services range from reliable message passing to fully ordered messages with delivery guarantees, even in case of computer failures and network partitions. Spread is designed to encapsulate the challenging aspects of asynchronous networks and enable the construction of scalable distributed applications, allowing application builders to focus on the differentiating components of their application.
There is of course a binding for Perl: Spread

HTH, Valerio

Replies are listed 'Best First'.
Re: Re: Instant Messaging Protocol
by simonm (Vicar) on Jan 05, 2004 at 17:41 UTC
Re: Re: Instant Messaging Protocol
by Eyck (Priest) on Jan 06, 2004 at 12:22 UTC

    Small problems with spread: it seems like it's more of a PVM/MPI replacement then universal messaging platform, and should run in perfectly-trusted environment.

    It seems like there is absolutely no authentication, and any user can pose as any other user/service, this may be fine in tight cluster, but what would you do if you wanted to send message 'Processing finished' to system programmers or support stuff?

    You'd need another messaging platform for that.

    Seems like secure spread fixes some of those consernes though...

    I wonder why it's so hard to get to protocol specs, all people publish these days are 'APIs'.