[ http://issues.apache.org/jira/browse/DIRMINA-144?page=comments#action_12360802 ]
Trustin Lee commented on DIRMINA-144: ------------------------------------- If this filter goes too phat, then we could split it into more than one small filters. Plus we need a way to limit the maximum number of unprocessed bytes, so too fast network doesn't lead the codec implementation to throw OutOfMemoryError. > Traffic shaping filter > ---------------------- > > Key: DIRMINA-144 > URL: http://issues.apache.org/jira/browse/DIRMINA-144 > Project: Directory MINA > Type: New Feature > Versions: 0.9 > Reporter: Niklas Therning > Priority: Minor > > MINA now has basic support for suspending/resuming reads and writes on an > IoSession for all transport types. We should use this feature to implement a > traffic shaping filter which lets the user configure bandwidth limitations. > Both globally and for individual sessions. Here are some configuration > options I can come to think of: > * Globally specify a maximum data rate for individual sessions (e.g. max 10 > kb/s for all sessions). > * Specify a maximum data rate on a per session basis (e.g. max 1 Mb/s for a > particular session). > * Specify a maximum upper limit on the bandwidth used by all sessions in > total (e.g. all sessions share a total of 10 Mb/s). > * Configure different traffic classes with different limits to allow for > high/low priority traffic and partition sessions into these priority classes. > I'm not sure how advanced it would have to be so please share your thoughts. > Maybe point 1 and 2 would suffice? I think 3 and 4 add a lot of complexity > since they need some kind of scheduling algorithm to provide fairness between > sessions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
