<div>
Hi,<br>
<br>
I've got an AMQP proxy that applies policy to the messages clients send
to a target AMQP host. I was considering re-implementing the current
Erlang proxy with libnl.<br>
<br>
I addition to what it already does, the proxy needs to:<br>
<ul>
<li>Throttle clients that exceed a ingress flow rate;</li>
<li>(Optionally) send back an AMQP frame to indicate to the
remote that it has been throttled;</li>
<li>Consume less resources than it currently does;<br>
</li>
</ul>
On face value, libnl-route appears to offer the features that can help
me not re-invent the wheel:<br>
<ul>
<li>Programmatic interception (and mangling I believe) of inbound
packets;</li>
<li>It has all of the queueing primitives;</li>
<li>As a framework, it has reasonably low processing overhead (for
non-kernel code);<br>
</li>
</ul>
So I was wondering if my assumptions are wrong and whether I am barking
up the wrong tree.<br>
<br>
Is this idea vaguely sane, or should I be looking elsewhere to achieve
my goal?<br>
<br>
Cheers,<br>
<br>
Ben
</div>
<div></div>