[rabbitmq-discuss] Java RabbitMQ API bug in response.getHeaders()?
tonygarnockjones+rabbitmq at gmail.com
Thu Oct 27 18:49:01 BST 2011
On 27 October 2011 13:36, Mario Leyton <mleyton at niclabs.cl> wrote:
> My feeling is that the rabbitmq teams is trying to aim for option A,
> while for me, as a user of the java client library it is easier to adopt
> rabbitmq client if it where built in terms of B.
I don't speak for the RabbitMQ team anymore, of course, but the philosophy
has in the past been that the client libraries should express the semantics
of AMQP, no more, no less, in as natural a way for the host language as
possible given the constraint of expressing exactly AMQP as she is spoke.
On top of that, where people figure out good patterns for working with AMQP
in a given host language, some of those have been included too in some
cases. Perhaps a wrapper that has an interface along the lines you suggest
would be a worthwhile inclusion.
Regarding the issue of the null check, I'd suggest looking at it
differently: instead of seeing the null check as *polluting* your code,
look at it as *paying attention to what the sender actually said*. The
check is necessary to fully understand the intention of the sender as
expressed using the facilities AMQP offers.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss