Comments on: Looking at AMQP http://stage.vambenepe.com/archives/26 William Vambenepe's stage Tue, 07 Feb 2012 23:33:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Ale http://stage.vambenepe.com/archives/26#comment-22 Ale Tue, 12 May 2009 11:46:13 +0000 http://stage.vambenepe.com/archives/26#comment-22 The cumbersome WS-Security model might be used to compensate the lack of encryption in AMQP. Was that the only critique for SOAP over AMQP? There is an Apache implementation... The cumbersome WS-Security model might be used to compensate the lack of encryption in AMQP. Was that the only critique for SOAP over AMQP? There is an Apache implementation…

]]> By: robert.j.greig@jpmorgan.com http://stage.vambenepe.com/archives/26#comment-21 robert.j.greig@jpmorgan.com Thu, 30 Nov 2006 02:41:05 +0000 http://stage.vambenepe.com/archives/26#comment-21 Hi, your comments are very interesting particularly since they are coming from a slightly different perspective to the one we have been focussing on. I am not very familiar with WS-Eventing, but I would be interested in exploring how we could map in detail to it. One comment I have is that, yes, you are right there would be two steps in the example you give, but notification to the publisher of interest in particular message types could be done using a queue - i.e. the publisher has a "register" queue that clients would send messages to and there would also be a topic for the publisher to broadcast out messages on. Using the "headers exchange" would allow easy filtering by clients for only events they are interested in. Regarding our topic exchange and its routing key rules, I presume that any hierarchy in WS-Topics is defined using XML. If so you could easily define a topic very similar to the current topic exchange that supported XML directly. The exchange model is extensible precisely for this reason. I would be interested in discussing your concerns about transactions and security in more detail. -- Robert (JP Morgan Chase) Hi, your comments are very interesting particularly since they are coming from a slightly different perspective to the one we have been focussing on.

I am not very familiar with WS-Eventing, but I would be interested in exploring how we could map in detail to it. One comment I have is that, yes, you are right there would be two steps in the example you give, but notification to the publisher of interest in particular message types could be done using a queue – i.e. the publisher has a “register” queue that clients would send messages to and there would also be a topic for the publisher to broadcast out messages on. Using the “headers exchange” would allow easy filtering by clients for only events they are interested in.

Regarding our topic exchange and its routing key rules, I presume that any hierarchy in WS-Topics is defined using XML. If so you could easily define a topic very similar to the current topic exchange that supported XML directly. The exchange model is extensible precisely for this reason.

I would be interested in discussing your concerns about transactions and security in more detail.

– Robert (JP Morgan Chase)

]]>