[rabbitmq-discuss] RabbitMQ ejabberd gateway

[Alex Clemesha]

Tony,

On Fri, Dec 5, 2008 at 8:55 AM, Tony Garnock-Jones <tonyg at lshift.net> wrote:
> Hi Alex,
>
> Sorry for the delay in addressing this. I hope it's still relevant.
Thanks for the response!  In fact, over the last two days, I was able to
solve all remaining issues that I had with this.

>
> Alex Clemesha wrote:
>>
>> 1) I can *only* use the exchange 'amq.topic' to perform the above
>> example where I send messages from XMPP to AMQP and vice-versa.
>> There *are* other exchanges in my AMQP network, because all
>> my AMQP producers and consumers use them at the same time I'm
>> trying the XMPP gateway, it just seems as though I can't make them
>> XMPP buddies.
>
> That's strange. Given a RabbitMQ/XMPP node running at rabbit.my.host.edu,
> try communicating with the JID "rabbit.my.host.edu" (i.e. without a node or
> resource part, a bare domain JID). Send it a message with just the word
> "list" in it, and it should send back a list of the exchanges it knows
> about. "list exchangename" should give you a list of bindings. Also, when
> adding a buddy to your buddy-list, if you become friends with
> "exchange at host/binding.pattern.#", the resource part is used in the
> queue.bind command. Similarly, when messages are delivered to you, the
> resource part of the from address is the routing-key from the message's
> publication.

Yes, communicating with the *bare* JID "rabbit.my.host.edu" was a crucial
piece that I was missing - for whatever reason I did not get this
*exact* requirement
from the documentation - I assume it is just a naive mistake on my part.



>
>> my question
>> is this: what would the password be for the JID
>> "amq.topic at rabbitmq.my.host.edu" that comes
>> into existence via the RabbitMQ gateway module for ejabberd?
>
> You can't log in as those JIDs. They're virtual, owned and controlled by the
> gateway code. Think of them as relay bots that are distant from you in the
> network. Your applications (endpoints) will have to have their own local
> JIDs, which when bound to remote exchange-JIDs will have proxy/relay queues
> created for them.

Yep, it is clear to me now ... got over the understanding learning curve
and now things are going great!


thanks,
Alex


> Cheers,
>  Tony
>



-- 
Alex Clemesha
clemesha.org