Traffic control

• Key: DIRMINA-2
• Type: New Feature
• Status: Closed
• Resolution: Fixed
• Priority: Minor
• Assignee: Trustin Lee
• Reporter: Trustin Lee
• Affects Version/s: 0.7.0, 0.8.0
• Fix Version/s: 0.9.0

Description

IoSession should have some traffic control methods to throttle traffic.
* IoSession.setTrafficMask( TrafficMask );

TrafficMask is an enumeration type consisted of
* NONE
* READ
* WRITE
* ALL

Comments

[Trustin Lee]

Following up new versioning strategy

[Trustin Lee]

We can rename IdleStatus to IoType and reuse it like this:
* IoSession.suspend( IoType )
* IoSession.resume( IoType )

[Trustin Lee]

Added a patch by Niklas Therning

[Trustin Lee]

Updated the issue description following to the recent changes.

[Niklas Therning]

Traffic control has now been implemented for all transports and has been checked in to trunk. As far as I can see this issue can now be closed.

NOTE: Traffic control for server side datagram sessions (originating from a DatagramAcceptor) will never happen since a new session is always created when new data is received. However, traffic control for sessions created using the DatagramConnector has been implemented.

Do you think we need to support the traffic control for server side datagram sessions? I don't see any working solution for this problem. If we cannot support the traffic control for server side daragrams, should we throw an UnsupportedOperationException, or just ignore the request silently?

[Trustin Lee]

I looked into your modification in detail. It looks really good! You did a great job. It was most impressive that you've got rid of VmPipeFilter. :)