Hi Harald,
> > Do you see other downsides to forwarding?
>
> you get the lowest TTL in the whole chain and god beware none of the
> multi-hop forwarders have a cache hit so it makes it to the last in chain
> doing then recursion - it's a simple "worst case math"
Do you ever have seen a signifi
Kevin Darcy wrote:
>
> In any case, multi-hop forwarding is always the least-preferred option.
>
I wonder for which reason do you think this.
Of course, any forwarding adds a additional hop and therefore additional delay
and an additional possible point of failure.
But this is true for any net
Hi,
To use two instances wouldn't help anything, he would need one instance with
two views and a second instance. Not a big win over three views.
But there is an easy solution with only two views. What the op seemes to have
missed in the docs is the following sentence:
"The order of the view s
3 matches
Mail list logo
