<div>Hmm, while cool, I'd really need the ability to use Basic.Properties. Given the single UDP packet restriction of the message, it's probably outside the realm of what I am looking for, but very cool none the less.</div><div><br></div><div>Gavin</div>
<div></div>
<p style="color: #A0A0A8;">On Tuesday, March 20, 2012 at 4:41 PM, Tony Garnock-Jones wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On 20 March 2012 16:40, Tony Garnock-Jones <span dir="ltr"><<a href="mailto:tonygarnockjones%2Brabbitmq@gmail.com">tonygarnockjones+rabbitmq@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div>
See <a href="https://github.com/tonyg/udp-exchange#readme" target="_blank">https://github.com/tonyg/udp-exchange#readme</a> under headings "Messages arriving from UDP" and "Messages to be sent to UDP".<br>
</div></blockquote><div><br>Um, to be slightly more informative: it simply takes the whole of the arriving UDP packet and sticks it in as the body of an AMQP message. It also copies as much of the packet as will fit into the routing key, after the string "ipv4.A.B.C.D.Port" where A.B.C.D is the source IP address. Bindings to the exchange get to use topic-exchange syntax for matching routing_keys.<br>
<br>Tony<br><br>
</div></div>
</div></div></span>
</blockquote>
<div>
<br>
</div>