Re: New extension proposal: SAM - Simple Asynchronous Messaging

On 29/09/06, Dave Renshaw <d.s.renshaw@googlemail.com> wrote:

The aim of the SAM extension is to open up the messaging infrastructure to the PHP scripting environment by providing an API that allows the most common and simple messaging operations to be accomplished with the minimum of fuss. At the same time the API has to allow for the fact that many of these messaging infrastructures are connecting legacy systems and thus it must be possible for someone skilled in messaging technologies to access the low-level details of messages and the associated gorp.

This looks goot to me - though I have seen another MQ based PECL module to do the same thing, though it was tied closer to the WMQ api. For myself, I'm architecting a system based on message passing, and right now the only middle-ware I'm really aware of that is really stable is IBM's MQ, though I'd prefer something that wasn't neccessarily Java based, as long as I can run it on a server somewhere and largely forget about it, I'd be happy. What I'd be really interested in is some idea of exactly I needed to be able to support a number of queue writers, and consumers in terms of hardware, servers and clients (just one server, or do I need multiple ones? Do I need to budget for clients, or just the central server?) Right now, I don't know, but I can see real advantages for scaling with an ESB-style distribution. I've not got a PHP.net account, but I give it a +1 vote anyway. Alister