On Thursday 04 October 2001 04:30 am, Rodent of Unusual Size wrote:
> Cliff Woolley wrote:
> > +1.  Port vs. Listen has always been one of the things
> > people just can't seem to figure out no matter how
> > carefully we try to explain it.  Doing it through
> > ServerName makes it much more clear what's going on.
>
> Due to the non-1:1 relationship between names and
> addresses, and that ports should be associated with
> IP addresses rather than names, I feel uncomfortable
> with the blanket statement above.

But Port hasn't been about selecting a port to listen to for a long time.
That is what Listen was for.  The only reason to have Port (in any situation
where you had multiple ports to listen to), was to have a way to tell the
server what port to report.

This removes the problem of having users put a Port directive in their config,
and two listen directives, and then wonder why the server was only listening
on two ports.  I have received three bug reports about this, this month alone.

Ryan

______________________________________________________________
Ryan Bloom                              [EMAIL PROTECTED]
Covalent Technologies                   [EMAIL PROTECTED]
--------------------------------------------------------------

Reply via email to