<div>Alexis<br></div>
<div>Thank you for your detailed answer.</div>
<div> </div>
<div>Isn't pubsub implementation in ejabberd + a custom client can address: </div>
<div> </div>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">AMQP is aimed at Business Messaging which means delivery semantics can<br>be much more specific ("at least once", "exactly once", "publish to<br>
these subscribers only", "persist", "be durable")</blockquote>
<div> </div>
<div>Does binary streams have any other advantage over xml other then smaller size?</div>
<div> </div>
<div>Is AMQP suitable for streaming video and audio?</div>
<div> </div>
<div>Can AMQP has something like http-bind (BOSH) implemented, letting web clients interact with the server.</div>
<div> </div>
<div>I've read the post about Reactor but didn't understand much.</div>
<div>Any news about that?</div>
<div> </div>
<div>Mark</div>
<div> </div></div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">On Sun, Jun 1, 2008 at 7:17 PM, Alexis Richardson <<a href="mailto:alexis.richardson@cohesiveft.com">alexis.richardson@cohesiveft.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Mark<br><br>This excellent blog post by Steve Jenson goes some way to addressing<br>your question.<br><br>
<a href="http://saladwithsteve.com/2007/08/future-is-messaging.html" target="_blank">http://saladwithsteve.com/2007/08/future-is-messaging.html</a><br><br>AMQP is aimed at Business Messaging which means delivery semantics can<br>
be much more specific ("at least once", "exactly once", "publish to<br>these subscribers only", "persist", "be durable"). This means that,<br>as Steve points out, the notion of 'presence' is replaced by the more<br>
general notion of a subscription. AMQP's model has routing exchanges<br>and queues which can be composed into pretty much any messaging<br>scenario. Finally, AMQP is a binary protocol whereas XMPP is XML.<br><br>All these characteristics make AMQP more fundamental in some sense.<br>
Really, it complements XMPP which is good at Instant Messaging. The<br>great thing about this is that large Instant Messaging infrastructures<br>exist and are used by lots of people. AMQP will be very good for<br>cases where human-human messaging is only a part of the solution - for<br>
example business integration and reactive event monitoring.<br><br>In terms of license and quality differences between ejabberd and<br>RabbitMQ - well they are both open source. RabbitMQ is MPL 1.1 and<br>(iirc) ejabberd is GPL. I think that because AMQP is more general and<br>
comprehensive than XMPP, it is arguably more 'extensible', and hence<br>so is RabbitMQ, but you may find it easier to locate XMPP tools as it<br>has been around for longer. RabbitMQ is a high quality implementation<br>
whose users often report happiness with its stability. That said,<br>ejabberd has been around even longer and its scalability and<br>manageability, is why we chose erlang for RabbitMQ :-)<br><br>If you wish to choose between ejabberd or RabbitMQ, then ask yourself<br>
if you are solving an XMPP type of problem or an AMQP type of problem.<br> Many solutions could quite happily use both. For example:<br><a href="http://blog.folknology.com/2008/05/31/reactored-my-packet-based-future-finally-emerges/" target="_blank">http://blog.folknology.com/2008/05/31/reactored-my-packet-based-future-finally-emerges/</a><br>
<br>Cheers,<br><br>alexis<br>
<div>
<div></div>
<div class="Wj3C7c"><br><br><br><br>On Sun, Jun 1, 2008 at 4:59 PM, mark peleus <<a href="mailto:mark.peleus@gmail.com">mark.peleus@gmail.com</a>> wrote:<br>> Hi,<br>><br>> Can anyone please explain the differences between AMPQ and XMPP.<br>
> Are both addressing the same problems?<br>><br>> What are the differences between RabbitMQ and ejabberd?<br>> Both are written in erlang.<br>> Is the only difference is the protocol they support or are there more<br>
> differences in quality, extensibility, license...?<br>><br>> Thanks<br>><br></div></div>> _______________________________________________<br>> rabbitmq-discuss mailing list<br>> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>><br>><br><font color="#888888"><br><br><br>
--<br>Alexis Richardson<br>+44 20 7617 7339 (UK)<br>+44 77 9865 2911 (cell)<br>+1 650 206 2517 (US)<br></font></blockquote></div><br>