My aim would be to get rid of MINA eventually... However there still needs to be some work to free the broker of dependence on Mina ByteBuffers etc (the I/O layer I've written just wraps the java.nio buffers in Mina buffers before passing them to the rest of the broker). I see that as a separate, but desirable, change.
As we are discussion, thought it would be good to throw what I have been looking to add on C++ broker into the mix. I want to create a policy that can be set per connection where you can specify a time derivative for messages, either in messages/sec or bytes/sec in a policy. This policy then would 'rate limit' a connection by only issuing credits to that limit for message transfer per rate interval. This would protect from a producer that has gone mad, by limiting the max bytes/messages any connection can pump into the broker.
it would also be possible to connect this to the queue depth policies we already have, but the
linkage from queue to connection is not always clear. Carl.
