Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Apr 2007 16:48:45 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>, Nate Lawson <nate@root.org>
Subject:   Re: libfetch ftp patch for less latency
Message-ID:  <200704181648.46348.jhb@freebsd.org>
In-Reply-To: <4617F563.40502@root.org>
References:  <460AE39B.4070706@root.org> <86ps6g5759.fsf@dwp.des.no> <4617F563.40502@root.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 07 April 2007 15:47, Nate Lawson wrote:
> Dag-Erling Sm=F8rgrav wrote:
> > Nate Lawson <nate@root.org> writes:
> >> Obviously, it's easier to do nothing than something.  So here are some
> >> options:
> >>
> >> 1. Add my patch -- if a server returns an error, I see no way it would
> >> have changed the PWD.  If you say "CD GARBAGE", what reasonable system
> >> would return an error and change to some random dir?
> >>
> >> 2. Add an env variable (similar to FTP_PASSIVE_MODE, say
> >> "FTP_SINGLE_CWD") which forces the current behavior.  If not set, fetch
> >> tries the multi-method first, falls back to the single-method on error.
> >=20
> > No.
> >=20
> > Thanks,
> >=20
> > DES
>=20
> I forgot:
>=20
> 3. #ifdef (on or off by default)
>=20
> Also, can I hear from anyone else besides Mr. No?

I'm hestitant to make fetch explicitly not follow the RFC.  At the least it
should follow the RFC by default.  Having it not follow the RFC actually
broke stuff at work until I fixed it.

=2D-=20
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704181648.46348.jhb>