On 27 October 2011 13:36, Mario Leyton <span dir="ltr"><<a href="mailto:mleyton@niclabs.cl">mleyton@niclabs.cl</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
My feeling is that the rabbitmq teams is trying to aim for option A,<br>
while for me, as a user of the java client library it is easier to adopt<br>
rabbitmq client if it where built in terms of B.<br></blockquote><div><br>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.<br>
<br>Regarding the issue of the null check, I'd suggest looking at it differently: instead of seeing the null check as <i>polluting</i> your code, look at it as <i>paying attention to what the sender actually said</i>. The check is necessary to fully understand the intention of the sender as expressed using the facilities AMQP offers.<br>
<br>Regards,<br>� Tony<br><br></div></div>