Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!uwvax!dave
From: dave@uwvax.UUCP (Dave Cohrs)
Newsgroups: net.mail
Subject: Re: Neighbor optimized away
Message-ID: <855@uwvax.UUCP>
Date: Fri, 2-May-86 15:30:53 EDT
Article-I.D.: uwvax.855
Posted: Fri May  2 15:30:53 1986
Date-Received: Sun, 4-May-86 06:01:39 EDT
References: <4509@dartvax.UUCP>
Organization: U of Wisconsin CS Dept
Lines: 24
Keywords: uucp pathalias

In article <4509@dartvax.UUCP>, steve@dartvax.UUCP (Steve Campbell) writes:
> It would be easy to hack uumail so that if in its right-to-left scan it
> finds a host which is an immediate neighbor, it stops there and doesn't
> even look in the database for a path.  Any thoughts on this situation?

Using uwvax as an example, we have a number of immediate neightbors, some
of which are very reliable, and some which only call us and really don't
call very often, for example, ihnp4.  Now, if a path optimizer here looked
through 'seismo!ihnp4!action' and noticed "Hey, we talk to ihnp4, I'll
queue it for them directly", it might never get there.  That's why the
cost in our map for ihnp4 is so high.

If you want to force your optimizer to choose a direct connection, lower
it's cost *locally* by adding an entry to your local pathalias input
file.  This way you can benefit from direct connections, without opening
the floodgates wide.

Disclaimer:  we don't optimize paths -- this is purely hypothetical.

-- 
Dave Cohrs
(608) 262-1204
...!{harvard,ihnp4,seismo,topaz}!uwvax!dave
dave@rsch.wisc.edu