Defines the message a router sends to another router in response to a
search (DatabaseFindNearest or DatabaseLookup) when it doesn't have the value,
specifying what routers it would search.
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
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
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
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
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.
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)
Decrypt the data from the specified record, writing the decrypted record into this instance's
buffer (but not overwriting the array contained within the old buffer)
Caution, do not make DEFAULT_OUTBOUND_BANDWIDTH * DEFAULT_SHARE_PCT > 32
without thinking about the implications (default connection limits, for example)
of moving the default bandwidth class from L to M, or maybe
adjusting bandwidth class boundaries.
We are the outbound tunnel gateway (we created it), so wrap up this message
with instructions to be forwarded to the targetPeer when it reaches the
endpoint.
We are the outbound tunnel gateway (we created it), so wrap up this message
with instructions to be forwarded to the targetTunnel on the targetPeer when
it reaches the endpoint.
for the 10 minutes after startup, don't fail db entries so that if we were
offline for a while, we'll have a chance of finding some live peers with the
previous references
Since the TimedWeightedPriorityMessageQueue.add()
was disabled by jrandom in UDPTransport.java
on 2006-02-19, and the choke/unchoke was disabled at the same time,
all of TWPMQ is pointless, so just do this for now.