net.i2p.router
Interface RouterThrottle

All Known Implementing Classes:
RouterThrottleImpl

public interface RouterThrottle

Gatekeeper for deciding whether to throttle the further processing of messages through the router. This is seperate from the bandwidth limiting which simply makes sure the bytes transferred dont exceed the bytes allowed (though the router throttle should take into account the current bandwidth usage and limits when determining whether to accept or reject certain activities, such as tunnels)


Method Summary
 boolean acceptNetDbLookupRequest(Hash key)
          Should we accept the netDb lookup message, replying either with the value or some closer peers, or should we simply drop it due to overload?
 boolean acceptNetworkMessage()
          Should we accept any more data from the network for any sort of message, taking into account our current load, or should we simply slow down?
 int acceptTunnelRequest(TunnelCreateMessage msg)
          Should we accept the request to participate in the given tunnel, taking into account our current load and bandwidth usage commitments?
 double getInboundRateDelta()
          How much faster (or if negative, slower) we are receiving data as opposed to our longer term averages?
 long getMessageDelay()
          How backed up we are at the moment processing messages (in milliseconds)
 long getTunnelLag()
          How backed up our tunnels are at the moment (in milliseconds)
 

Method Detail

acceptNetworkMessage

public boolean acceptNetworkMessage()
Should we accept any more data from the network for any sort of message, taking into account our current load, or should we simply slow down?


acceptTunnelRequest

public int acceptTunnelRequest(TunnelCreateMessage msg)
Should we accept the request to participate in the given tunnel, taking into account our current load and bandwidth usage commitments?

Returns:
0 if it should be accepted, higher values for more severe rejection

acceptNetDbLookupRequest

public boolean acceptNetDbLookupRequest(Hash key)
Should we accept the netDb lookup message, replying either with the value or some closer peers, or should we simply drop it due to overload?


getMessageDelay

public long getMessageDelay()
How backed up we are at the moment processing messages (in milliseconds)


getTunnelLag

public long getTunnelLag()
How backed up our tunnels are at the moment (in milliseconds)


getInboundRateDelta

public double getInboundRateDelta()
How much faster (or if negative, slower) we are receiving data as opposed to our longer term averages?