I2P_Developers/i2p.android.base
3
0
Fork 2
Code Issues 39 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

* SSU: Don't offer to introduce when near connection limit

Browse Source
This commit is contained in:
zzz
2009-05-24 00:29:18 +00:00
parent c75ff538a3
commit f4fdbceb3b
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
router/java/src/net/i2p/router/transport/udp/EstablishmentManager.java
View File

@ -282,7 +282,10 @@ public class EstablishmentManager {
}
if (isNew) {
// we don't expect inbound connections when hidden, but it could happen
if ((!_context.router().isHidden()) && !_transport.introducersRequired()) {
// Don't offer if we are approaching max connections. While Relay Intros do not
// count as connections, we have to keep the connection to this peer up longer if
// we are offering introductions.
if ((!_context.router().isHidden()) && (!_transport.introducersRequired()) && _transport.haveCapacity()) {
long tag = _context.random().nextLong(MAX_TAG_VALUE);
state.setSentRelayTag(tag);
if (_log.shouldLog(Log.INFO))
@ -570,7 +573,8 @@ public class EstablishmentManager {
private void sendCreated(InboundEstablishState state) {
long now = _context.clock().now();
if (!_transport.introducersRequired()) {
// don't offer if we are approaching max connections (see comments above)
if ((!_transport.introducersRequired()) && _transport.haveCapacity()) {
// offer to relay
// (perhaps we should check our bw usage and/or how many peers we are
// already offering introducing?)