On 22/08/07, Rajith Attapattu <[EMAIL PROTECTED]> wrote:
> >
> > But not one that allows access to AMQP functionality. I don't see why
> > the AMQP WG couldn't provide a set of Interfaces and a client lib
> > could then implement jmx.Session and amqp.Session. Then again I've
> > never had any exposure to CORBA to know what they did wrong. Is the
> > lesson simply never to provide an API? That seems a bit harsh.
> >
>
> Two reasons.
> Defining an API is time consuming and difficult given the no of languages we
> have.
> Also they differ from object oriented to procedural to functional.
> So obviously there will be different views on how best it should be done in
> a given language.
> I heard of client implementations in the following languages so far.
> java, c++, python, ruby, erlang? , javascript - and most like C and perl.
>
> The second reason is more political.
> I think it is a very difficult exercise to get agreement over the API from
> different vendors.
> Everybody will think their API is the best - atleast thats what happend with
> CORBA.
> http://portal.acm.org/citation.cfm?id=1142044&coll=GUIDE&dl=GUIDE&CFID=24831971&CFTOKEN=13722890&ret=1#Fulltext

Interesting read. Seems like the major problem wasn't the existence of
the API but more the WG inability to weed out the poor ideas and just
throw everything in. From what I've seen the AMQP WG is much tighter
and more focused on a cohesive solution. AMQP also has a number of
implementations that will help work out the wire level protocol. Where
as CORBA didn't have any.

Not sure the article argues that having an API is a bad thing. In fact
the lack of a .NET binding was cited as part of the downfall.

I think we should be developing our qpid API, as we are doing, then
extracting the interfaces and suggesting them to the AMQP WG, it would
be a good starting point for any given languages API. The fact that we
suggested the API to the AMQP WG doesn't mean they have to accept it
but with feedback from users about its the ease of use then that would
help the WG, form an opinion and direction to take.




> Regards,
>
> Rajith
>


-- 
Martin Ritchie

Reply via email to