net.i2p.router

Class RouterDoSThrottle

java.lang.Object

net.i2p.router.RouterThrottleImpl

net.i2p.router.RouterDoSThrottle

All Implemented Interfaces:

RouterThrottle

Deprecated.

unused

@Deprecated
class RouterDoSThrottle
extends RouterThrottleImpl

Minor extention of the router throttle to handle some DoS events and throttle accordingly.

Field Summary

Fields inherited from class net.i2p.router.RouterThrottleImpl

_context, DEFAULT_MAX_TUNNELS, PROP_MAX_TUNNELS, TUNNEL_ACCEPT

Constructor Summary

Constructors

Constructor and Description
RouterDoSThrottle(RouterContext context) Deprecated.

Method Summary

Modifier and Type	Method and Description
boolean	acceptNetDbLookupRequest(net.i2p.data.Hash key) Deprecated. 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?

Methods inherited from class net.i2p.router.RouterThrottleImpl

acceptNetworkMessage, acceptTunnelRequest, cancelShutdownStatus, getInboundRateDelta, getLocalizedTunnelStatus, getMessageDelay, getTunnelLag, getTunnelStatus, setShutdownStatus, setTunnelStatus

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

RouterDoSThrottle

public RouterDoSThrottle(RouterContext context)

Deprecated.

Method Detail

acceptNetDbLookupRequest

public boolean acceptNetDbLookupRequest(net.i2p.data.Hash key)

Deprecated.

Description copied from interface: RouterThrottle

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?

Specified by:

acceptNetDbLookupRequest in interface RouterThrottle

Overrides:

acceptNetDbLookupRequest in class RouterThrottleImpl