Bandwidth throttle/limit for set of channels

[Thingfish]

Hi

I'm looking at using netty for a file transfer app, where I need to be able
to set artificial limits on the total upload/download bandwidth used by a
set of channels (incoming as well as outgoing connections). Have been
browsing the code repository for this feature, but it seems that previous
attempts at implementing throttling has been deleted?

Assuming this feature is not already present, I was wondering if anyone has
considered how it could be done and what traps to look out for in respect to
nio and the tread model? The solution I've considered involves a token
bucket structure shared between the regulated channels, which contains a
seperate bucket for up and download. The problem is how to handle the
temporary "block"/wait occuring when one of the buckets are empty, since
just blocking the netty worker thread would prevent handling requests for
the other (up/down) resource even if it isnt exhausted. 


-- 
View this message in context: http://n2.nabble.com/Bandwidth-throttle-limit-for-set-of-channels-tp3986605p3986605.html
Sent from the Netty User Group mailing list archive at Nabble.com.