Gordon Sim wrote:
James Mansion wrote:
Sure you couldn't have a C API that is closely based on the MQSeries
one, with extra tweaks?
Or a C++ API that is much like the COM API from MSMQ?
Both with extensions as needed.
These are the most widely deployed existing systems. Sure you're not
going to design a bikeshed?
Are there specific aspects of either of those two APIs that you would
like to emulate? Or are you just suggesting that we reuse an existing
API?
Both, but the attraction of MQSeries particularly is the simplicity.
And, to be honest, its the market leader.
My question is: why do you feel the need to create something materially
different, and why in particular does
a messaging API need to be much more complex for normal use?
It won't be usable as-is, but the simplicity is simething to aspire to.
Were there an existing API open standard for messaging in c++ I would
be very keen for us to embrace it.
A simple C API would arguably be more useful though, and easier to
explain to users of scripting languages.
I suspect it would be acceptable to implement with C++ and depend on
installed C++ support,
even if that's not ideal long term.
Since when did an API have to be open to be copied anyway?
James
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
