On Monday 17 November 2003 06:38 pm, Toad wrote:
On Sun, Nov 16, 2003 at 11:37:37PM -0500, Ed Tomlinson wrote:
HTL does not get decremented until we can route. So a QR will not
cause the cascade. For that to happen we need to find the data or
get a DNF...
HTL is however decremented on a
On Fri, Nov 21, 2003 at 01:34:09PM -0600, Tom Kaitchuck wrote:
On Monday 17 November 2003 06:38 pm, Toad wrote:
On Sun, Nov 16, 2003 at 11:37:37PM -0500, Ed Tomlinson wrote:
HTL does not get decremented until we can route. So a QR will not
cause the cascade. For that to happen we need
Toad [EMAIL PROTECTED] writes:
I do now. However, it is a way that a node could hurt the network
without being proportionately punished for it in the estimators - if I
reinstate it, then nodes that QR with HTL 0, killing the request, will be
treated the same as nodes that QR at any other HTL.
On Thu, Nov 20, 2003 at 11:58:45AM -0600, Edgar Friendly wrote:
Toad [EMAIL PROTECTED] writes:
I do now. However, it is a way that a node could hurt the network
without being proportionately punished for it in the estimators - if I
reinstate it, then nodes that QR with HTL 0, killing the
Toad wrote:
On Thu, Nov 20, 2003 at 11:58:45AM -0600, Edgar Friendly wrote:
Toad [EMAIL PROTECTED] writes:
I do now. However, it is a way that a node could hurt the network
without being proportionately punished for it in the estimators - if I
reinstate it, then nodes that QR with HTL 0, killing
On Sun, 2003-11-16 at 23:37, Ed Tomlinson wrote:
On November 16, 2003 10:17 pm, Edward J. Huff wrote:
I'm very confused by this. I was under the impression that a
QR meant DON'T back down the chain, just try another path and
that DNF meant send a failure all the way back down the chain,
Edward J. Huff [EMAIL PROTECTED] writes:
On Sun, 2003-11-16 at 21:40, Ken Corson wrote:
Edward J. Huff wrote:
Thanks for the confidence, but I don't know everything. I took
the guy you corrected as being right because I got behind reading
this list and thought that no one corrected _his_
Edward J. Huff [EMAIL PROTECTED] writes:
... Now I see. I only knew about QR's in the context of node
overload, not in their normal context, which occurs when the
key is found in the failure table or when (I guess) the node
can't find a route. I've read only a small fraction of the code.
On Sun, Nov 16, 2003 at 08:59:50PM -0500, Edward J. Huff wrote:
Many nodes now exceed their output bandwidth regularly and as a
result issue many QRs. We are trying to reduce the bandwidth wasted
sending QRs, and the waste of resources which occurs when a deeply
chained request gets QRed.
On Sun, Nov 16, 2003 at 11:37:37PM -0500, Ed Tomlinson wrote:
HTL does not get decremented until we can route. So a QR will not
cause the cascade. For that to happen we need to find the data or
get a DNF...
HTL is however decremented on a QR to prevent load explosion on a
single request.
On Mon, Nov 17, 2003 at 06:52:49AM -0500, Edward J. Huff wrote:
On Sun, 2003-11-16 at 23:37, Ed Tomlinson wrote:
On November 16, 2003 10:17 pm, Edward J. Huff wrote:
I'm very confused by this. I was under the impression that a
QR meant DON'T back down the chain, just try another path
On Mon, Nov 17, 2003 at 02:28:13PM -0600, Edgar Friendly wrote:
Edward J. Huff [EMAIL PROTECTED] writes:
... Now I see. I only knew about QR's in the context of node
overload, not in their normal context, which occurs when the
key is found in the failure table or when (I guess) the node
On Tue, Nov 18, 2003 at 12:45:59AM +, Toad wrote:
QueryRejected.java:
This paragraph is confusing and poorly worded; a better way of saying
what was intended is:
* This message is sent by a node that cannot continue the request for
* a piece of data. If recieved by a node, it
Many nodes now exceed their output bandwidth regularly and as a
result issue many QRs. We are trying to reduce the bandwidth wasted
sending QRs, and the waste of resources which occurs when a deeply
chained request gets QRed. The node which first receives the QR
does not try again with a
On Sun, 2003-11-16 at 21:40, Ken Corson wrote:
Edward J. Huff wrote:
chained request gets QRed. The node which first receives the QR
does not try again with a different node in its routing table, as
it would if it got a DNF. Instead, it passes the QR back, and
all of the preceding links
On November 16, 2003 10:17 pm, Edward J. Huff wrote:
I'm very confused by this. I was under the impression that a
QR meant DON'T back down the chain, just try another path and
that DNF meant send a failure all the way back down the chain,
as the HTL has been exhausted.
In fact, that's
16 matches
Mail list logo
