net.i2p.router.peermanager

Class ProfileManagerImpl

java.lang.Object

net.i2p.router.peermanager.ProfileManagerImpl

All Implemented Interfaces:

ProfileManager

public class ProfileManagerImpl
extends Object
implements ProfileManager

Methods to update profiles. Unless otherwise noted, methods are blocking on the reorganize lock.

Constructor Summary

Constructors

Constructor and Description
ProfileManagerImpl(RouterContext context)

Method Summary

Modifier and Type	Method and Description
void	commErrorOccurred(net.i2p.data.Hash peer) Note that there was some sort of communication error talking with the peer
void	dbLookupFailed(net.i2p.data.Hash peer) Note that the peer was unable to reply to a db lookup - either with data or with a lookupReply redirecting the user elsewhere This will force creation of DB stats Non-blocking.
void	dbLookupReceived(net.i2p.data.Hash peer) Note that the local router received a db lookup from the given peer Non-blocking.
void	dbLookupReply(net.i2p.data.Hash peer, int newPeers, int oldPeers, int invalid, int duplicate, long responseTimeMs) Note that the peer replied to a db lookup with a redirect to other routers, where the list of redirected users included newPeers routers that the local router didn't know about, oldPeers routers that the local router already knew about, the given invalid routers that were invalid in some way, and the duplicate number of routers that we explicitly asked them not to send us, but they did anyway Non-blocking.
void	dbLookupSuccessful(net.i2p.data.Hash peer, long responseTimeMs) Note that the peer was able to return the valid data for a db lookup This will force creation of DB stats Non-blocking.
void	dbStoreFailed(net.i2p.data.Hash peer) Note that we were unable to confirm a successful send of db data to the peer, at least not within our timeout period This will force creation of DB stats
void	dbStoreReceived(net.i2p.data.Hash peer, boolean wasNewKey) Note that the local router received an unprompted db store from the given peer Non-blocking.
void	dbStoreSent(net.i2p.data.Hash peer, long responseTimeMs) Note that we've confirmed a successful send of db data to the peer (though we haven't necessarily requested it again from them, so they /might/ be lying) This is not really interesting, since they could be lying, so we do not increment any DB stats at all.
void	dbStoreSuccessful(net.i2p.data.Hash peer) Note that we've verified a successful send of db data to the floodfill peer by querying another floodfill.
void	heardAbout(net.i2p.data.Hash peer) Note that the local router received a reference to the given peer, either through an explicit dbStore or in a dbLookupReply Non-blocking.
void	heardAbout(net.i2p.data.Hash peer, long when) Note that the local router received a reference to the given peer at a certain time.
void	messageFailed(net.i2p.data.Hash peer) Note that the router failed to send a message to the peer over any transport.
void	messageFailed(net.i2p.data.Hash peer, String transport) Note that the router failed to send a message to the peer over the transport specified.
void	messageReceived(net.i2p.data.Hash peer, String style, long msToReceive, int bytesRead) Note that the router received a message from the given peer on the specified transport.
void	messageSent(net.i2p.data.Hash peer, String transport, long msToSend, long bytesSent) Note that it took msToSend to send a message of size bytesSent to the peer over the transport.
void	tunnelDataPushed(net.i2p.data.Hash peer, long rtt, int size) Non-blocking.
void	tunnelDataPushed1m(net.i2p.data.Hash peer, int size) Non-blocking.
void	tunnelFailed(net.i2p.data.Hash peer, int pct) Note that the peer participated in a tunnel that failed.
void	tunnelJoined(net.i2p.data.Hash peer, long responseTimeMs) Note that the router agreed to participate in a tunnel
void	tunnelLifetimePushed(net.i2p.data.Hash peer, long lifetime, long size) Non-blocking.
void	tunnelRejected(net.i2p.data.Hash peer, long responseTimeMs, int severity) Note that a router explicitly rejected joining a tunnel.
void	tunnelTestSucceeded(net.i2p.data.Hash peer, long responseTimeMs) Note that a tunnel that the router is participating in was successfully tested with the given round trip latency Non-blocking.
void	tunnelTimedOut(net.i2p.data.Hash peer) Note that a router did not respond to a tunnel join.

Methods inherited from class java.lang.Object

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

Constructor Detail

ProfileManagerImpl

public ProfileManagerImpl(RouterContext context)

Method Detail

messageSent

public void messageSent(net.i2p.data.Hash peer,
                        String transport,
                        long msToSend,
                        long bytesSent)

Note that it took msToSend to send a message of size bytesSent to the peer over the transport. This should only be called if the transport considered the send successful. Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

messageSent in interface ProfileManager

messageFailed

public void messageFailed(net.i2p.data.Hash peer,
                          String transport)

Note that the router failed to send a message to the peer over the transport specified. Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

messageFailed in interface ProfileManager

messageFailed

public void messageFailed(net.i2p.data.Hash peer)

Note that the router failed to send a message to the peer over any transport. Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

messageFailed in interface ProfileManager

commErrorOccurred

public void commErrorOccurred(net.i2p.data.Hash peer)

Note that there was some sort of communication error talking with the peer

Specified by:

commErrorOccurred in interface ProfileManager

tunnelJoined

public void tunnelJoined(net.i2p.data.Hash peer,
                         long responseTimeMs)

Note that the router agreed to participate in a tunnel

Specified by:

tunnelJoined in interface ProfileManager

tunnelRejected

public void tunnelRejected(net.i2p.data.Hash peer,
                           long responseTimeMs,
                           int severity)

Note that a router explicitly rejected joining a tunnel.

Specified by:

tunnelRejected in interface ProfileManager

Parameters:

responseTimeMs - ignored

severity - how much the peer doesnt want to participate in the tunnel (large == more severe)

peer - who rejected us

tunnelTimedOut

public void tunnelTimedOut(net.i2p.data.Hash peer)

Note that a router did not respond to a tunnel join. Since TunnelHistory doesn't have a timeout stat, pretend we were rejected for bandwidth reasons.

Specified by:

tunnelTimedOut in interface ProfileManager

Parameters:

peer - who rejected us

tunnelTestSucceeded

public void tunnelTestSucceeded(net.i2p.data.Hash peer,
                                long responseTimeMs)

Note that a tunnel that the router is participating in was successfully tested with the given round trip latency Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

tunnelTestSucceeded in interface ProfileManager

tunnelDataPushed

public void tunnelDataPushed(net.i2p.data.Hash peer,
                             long rtt,
                             int size)

Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

tunnelDataPushed in interface ProfileManager

tunnelDataPushed1m

public void tunnelDataPushed1m(net.i2p.data.Hash peer,
                               int size)

Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

tunnelDataPushed1m in interface ProfileManager

tunnelLifetimePushed

public void tunnelLifetimePushed(net.i2p.data.Hash peer,
                                 long lifetime,
                                 long size)

Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

tunnelLifetimePushed in interface ProfileManager

tunnelFailed

public void tunnelFailed(net.i2p.data.Hash peer,
                         int pct)

Note that the peer participated in a tunnel that failed. Its failure may not have been the peer's fault however. Blame the peer with a probability of pct/100.

Specified by:

tunnelFailed in interface ProfileManager

dbLookupSuccessful

public void dbLookupSuccessful(net.i2p.data.Hash peer,
                               long responseTimeMs)

Note that the peer was able to return the valid data for a db lookup This will force creation of DB stats Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

dbLookupSuccessful in interface ProfileManager

dbLookupFailed

public void dbLookupFailed(net.i2p.data.Hash peer)

Note that the peer was unable to reply to a db lookup - either with data or with a lookupReply redirecting the user elsewhere This will force creation of DB stats Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

dbLookupFailed in interface ProfileManager

dbLookupReply

public void dbLookupReply(net.i2p.data.Hash peer,
                          int newPeers,
                          int oldPeers,
                          int invalid,
                          int duplicate,
                          long responseTimeMs)

Note that the peer replied to a db lookup with a redirect to other routers, where the list of redirected users included newPeers routers that the local router didn't know about, oldPeers routers that the local router already knew about, the given invalid routers that were invalid in some way, and the duplicate number of routers that we explicitly asked them not to send us, but they did anyway Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

dbLookupReply in interface ProfileManager

dbLookupReceived

public void dbLookupReceived(net.i2p.data.Hash peer)

Note that the local router received a db lookup from the given peer Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

dbLookupReceived in interface ProfileManager

dbStoreReceived

public void dbStoreReceived(net.i2p.data.Hash peer,
                            boolean wasNewKey)

Note that the local router received an unprompted db store from the given peer Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

dbStoreReceived in interface ProfileManager

dbStoreSent

public void dbStoreSent(net.i2p.data.Hash peer,
                        long responseTimeMs)

Note that we've confirmed a successful send of db data to the peer (though we haven't necessarily requested it again from them, so they /might/ be lying) This is not really interesting, since they could be lying, so we do not increment any DB stats at all. On verify, call dbStoreSuccessful().

Specified by:

dbStoreSent in interface ProfileManager

Parameters:

responseTimeMs - ignored

dbStoreSuccessful

public void dbStoreSuccessful(net.i2p.data.Hash peer)

Note that we've verified a successful send of db data to the floodfill peer by querying another floodfill. This will force creation of DB stats

Specified by:

dbStoreSuccessful in interface ProfileManager

dbStoreFailed

public void dbStoreFailed(net.i2p.data.Hash peer)

Note that we were unable to confirm a successful send of db data to the peer, at least not within our timeout period This will force creation of DB stats

Specified by:

dbStoreFailed in interface ProfileManager

heardAbout

public void heardAbout(net.i2p.data.Hash peer)

Note that the local router received a reference to the given peer, either through an explicit dbStore or in a dbLookupReply Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

heardAbout in interface ProfileManager

heardAbout

public void heardAbout(net.i2p.data.Hash peer,
                       long when)

Note that the local router received a reference to the given peer at a certain time. Only update the time if newer. Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

heardAbout in interface ProfileManager

messageReceived

public void messageReceived(net.i2p.data.Hash peer,
                            String style,
                            long msToReceive,
                            int bytesRead)

Note that the router received a message from the given peer on the specified transport. Messages received without any "from" information aren't recorded through this metric. If msToReceive is negative, there was no timing information available. Non-blocking. Will not update the profile if we can't get the lock.

Specified by:

messageReceived in interface ProfileManager