On 04/06/07, Tomas Restrepo <[EMAIL PROTECTED]> wrote:
I agree this is a valid question, but at least from my point of view, uniformity of the API isn't such a big deal, for this kind of project in particular. That said, if the API were to be that AMQP-compatible API, which is certainly fairly low level, then by that virtue alone the API would be fairly similar across implementations, simply because it would resemble the AMQP class/method model fairly closely. I believe we'd likely still have some differences for things async operations (which definitely have different conventions across languages), but that wouldn't be that bad.
I can be brought round to this point of view. As you rightly point out the API is going to look like the protocol anyway. Also Robert Greigs post about developers using the appropriate API for their language and that being the one to implement, clarifies what is more important. Rupert
