<br><br><div class="gmail_quote">On Wed, Nov 12, 2008 at 6:03 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Peter,<br>
<div class="Ih2E3d"><br>
On Tue, Nov 11, 2008 at 10:12 PM, Peter Silva <<a href="mailto:Peter.A.Silva@gmail.com">Peter.A.Silva@gmail.com</a>> wrote:<br>
> I would really appreciate someone who understands switching having a look at<br>
> our switch. We've only used it internally so far, but I whipped up some<br>
> .deb's in honour of your request:<br>
<br>
</div>I don't know If I'm the best qualified person to do this. Due to the<br>
fact however that I have a large backlog of Rabbit specific items to<br>
get through, this will have to be appended to that queue, so I won't<br>
be able to look at this straight away. You might get a response from<br>
somebody else on the list, hence why I forwarded this mail.<br>
<div class="Ih2E3d"></div></blockquote><div><br>um... ok...<br>I guess one should't say 'show me the code' if one isn't prepared to look at it. OTOH, being presented with the whole pile is a bit much to chew off... maybe it can be easier...<br>
<br>if you install the package (It doesn't run by default) and do a man of pxReceiver, there is a section 'PRODUCT ROUTING OPTIONS' which describes the algorithm from the AMQP 'exchange' point of view in a paragraph or two. In the pxSender man page, there is an analogous section, called 'PRODUCT SELECTION OPTIONS' which is two paragraphs. The code implements what is in the two sections, and that's all.<br>
<br>but hey, this is a rabbit list, I only brought it up in order to share impressions about how the bindings are defined in AMQP. <br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> The reason for me asking these questions is to understand how to add AMQP<br>
> support to metpx.<br>
<br>
</div>Are you more interested in implementing some form of the AMQP<br>
model/codec in metpx or are you interested in being a consumer of AMQP<br>
(e.g. via Rabbit)?</blockquote><div><br>I'm hoping one of my developers can do a producer to speak to rabbit. I would send a single, un-differentiated product stream, and pilot having a few clients (internal first, external later) use the consumer of their choice to acquire the messages. I have a business need that no other package (including metpx) currently fills, that rabbit seems, at first blush, perfect for.<br>
<br>It is likely that we have to implement a consumer just to test the sender with metpx. Adding amqp service/broker functions doesn't seem like much of a stretch, but there isn't a business case right now (rabbit exists!) just use what's there for what it's good for.<br>
<br>What could be in it for rabbit...<br>Does rabbit want some protocol drivers? We have solid ones for FTP and SFTP. I doubt you'd be interested in the others... similarly to the way I was looking at using rabbit to provide functionality that isn't in metpx. rabbit might just want to use metpx as a realy sympathetic protocol driver. Just looking for win-win... ymmv.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
If the former is the case, then maybe approaching the AMQP working<br>
group might prove more fruitful that speaking to an implementer of<br>
AMQP.</blockquote><div><br>I would, except when I went to the AMQP lists I could see, they were dead. maybe I didn't find the right ones. The action seems to be over here, plus the whole routing thing was just an aside from reading the above, my aim is what was described above. <br>
<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<font color="#888888"><br>
Ben<br>
</font></blockquote></div><br>