| Author |
Message |
|
| tonyg |
 Posted: Tue Jul 01, 2008 12:38 pm |
 |
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
|
| Back to top |
  
|
| Guest |
| Posted: Tue Jul 01, 2008 1:10 pm |
|
|
|
Guest
|
Hi Tony,
This definitely sounds cool. I'll try to install it and play around
with. This also seems like a way to do some kind of Human Management
Interface.
Regards,
Michael Arnoldus
On Jul 1, 2008, at 14:38 , Tony Garnock-Jones wrote:
> Hi all,
>
> I |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Jul 02, 2008 2:27 pm |
|
|
|
Guest
|
Nice!
What way did you choose to encode AMQP binary messages? XEP-0047?
Martin
Tony Garnock-Jones wrote:
> Hi all,
>
> I |
|
|
| Back to top |
|
| alexis |
| Posted: Wed Jul 02, 2008 3:08 pm |
|
|
|
User
Joined: 06 Sep 2007
Posts: 80
Location: London
|
Michael
Exactly. If you click through to the linked docs, there is some
discussion about how to manage RabbitMQ over IM.
http://hg.rabbitmq.com/rabbitmq-xmpp/raw-file/tip/doc/index.html
alexis
On Tue, Jul 1, 2008 at 2:09 PM, Michael Arnoldus <chime@mu.dk> wrote:
> Hi Tony,
>
> This definitely sounds cool. I'll try to install it and play around with.
> This also seems like a way to do some kind of Human Management Interface.
>
> Regards,
>
> Michael Arnoldus
>
> On Jul 1, 2008, at 14:38 , Tony Garnock-Jones wrote:
>
>> Hi all,
>>
>> I'm pleased to announce that our XMPP gateway for exposing AMQP services
>> to the global XMPP network has been released.
>>
>> By bridging between the two systems, we benefit from:
>>
>> * XMPP's internet-scale addressing and federation
>> * XMPP's presence model
>> * AMQP's store-and-forward capability
>> * AMQP's routing and filtering (using exchanges and bindings)
>>
>> The current implementation is a very simple mapping between the two
>> systems. Its simplicity keeps the code short, but only exposes a subset
>> of AMQP features to the XMPP network, and vice versa.
>>
>> The full announcement, with links to documentation and downloads, is
>> available at
>> http://www.lshift.net/blog/2008/07/01/rabbitmq-xmpp-gateway-released.
>>
>> I'd be very interested in any feedback on the current approach and any
>> suggestions as to alternative ways of integrating the two networks.
>>
>> Regards,
>> Tony
>> --
>> [][][] Tony Garnock-Jones | Mob: +44 (0)7905 974 211
>> [][] LShift Ltd | Tel: +44 (0)20 7729 7060
>> [] [] http://www.lshift.net/ | Email: tonyg@lshift.net
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss@lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss@lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
--
Alexis Richardson
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Wed Jul 02, 2008 4:33 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Martin Sustrik wrote:
> Nice!
> What way did you choose to encode AMQP binary messages? XEP-0047?
 We didn't yet. So far, it's plain-text only. XEP-0047 doesn't look
appropriate: I think XEP-0231 looks like the one to use instead.
I wonder whether the implied semantics of <message/> is
multipart/alternative or multipart/related?
XEP 79 looks interesting, from an AMQP perspective!
XEP 184 could be interesting.
I will have to read XEP 60 in some detail fairly soon, no doubt.
Tony
--
[][][] Tony Garnock-Jones | Mob: +44 (0)7905 974 211
[][] LShift Ltd | Tel: +44 (0)20 7729 7060
[] [] http://www.lshift.net/ | Email: tonyg@lshift.net
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Wed Jul 02, 2008 4:38 pm |
|
|
|
Guest
|
Still, XEP-0239 can be used
Tony Garnock-Jones wrote:
> Martin Sustrik wrote:
>> Nice!
>> What way did you choose to encode AMQP binary messages? XEP-0047?
>
> We didn't yet. So far, it's plain-text only. XEP-0047 doesn't look
> appropriate: I think XEP-0231 looks like the one to use instead.
>
> I wonder whether the implied semantics of <message/> is
> multipart/alternative or multipart/related?
>
> XEP 79 looks interesting, from an AMQP perspective!
>
> XEP 184 could be interesting.
>
> I will have to read XEP 60 in some detail fairly soon, no doubt.
>
> Tony
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
| tonyg |
| Posted: Wed Jul 02, 2008 8:23 pm |
|
|
|
User
Joined: 07 Nov 2006
Posts: 199
|
Whoa! Super efficient!
Martin Sustrik wrote:
> Still, XEP-0239 can be used
>
> Tony Garnock-Jones wrote:
>> Martin Sustrik wrote:
>>> Nice!
>>> What way did you choose to encode AMQP binary messages? XEP-0047?
>>
>> We didn't yet. So far, it's plain-text only. XEP-0047 doesn't look
>> appropriate: I think XEP-0231 looks like the one to use instead.
>>
>> I wonder whether the implied semantics of <message/> is
>> multipart/alternative or multipart/related?
>>
>> XEP 79 looks interesting, from an AMQP perspective!
>>
>> XEP 184 could be interesting.
>>
>> I will have to read XEP 60 in some detail fairly soon, no doubt.
>>
>> Tony
>
>
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss@lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
Post received from mailinglist |
|
|
| Back to top |
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
