According to Geoff Hutchison:
> At 1:47 PM -0600 11/26/99, Gilles Detillieux wrote:
> >primarily with 3.1.4 in mind. While there isn't an official feature
> >freeze in place, I'm being pretty strict about what I'm putting in
> >there myself.
>
> No, though the whole 3-1-x branch is essentially under feature-freeze
> from before the 3.1.0 release.
Oh, should I have asked for a vote on all the enhancements I've put in,
or do votes for stuff in 3.2.0b1 also count for 3.1.4 if feasible? I can
say that I've tested my enhancements pretty carfully.
> > > 3) htdig/Retriever.cc & htdig/Server.cc: modified to allow local file
> > > access to persist even if the HTTP server is down. Looks good to me.
> >
> >Unless anyone objects, I'd like this to go into 3.1.4. For 3.2.0b1, we
> >need a vote. Here's my +1!
>
> I'll give +1 as well.
> If this goes in, it will actually be fairly trivial to implement
> grabbing robots.txt from the filesystem--the Server class will know
> whether it's supposed to be going local. I'll be glad to implement
> this as well as the oft-requested "only local" option where it
> doesn't go to HTTP on failure. I'll give this the config attribute
> "local_only."
My choice would be local_urls_only, because it is directly related to the
local_urls option. I'd like to backport this to 3.1.4, as it nicely
dovetails with Alexis's changes. I'd also like to merge GetLocal() and
GetLocalUser(), as there's some duplication of code happening, both for
the handling of local_default_doc (which I'd like to expand to use a
string list), and because we'll now be calling GetLocal() from at least
3 places, and needing to check GetLocalUser() at those same places.
I think it makes sense, logically, to group the two into one function, or
have one call the other.
> Actually, if no one objects, I'll install the Server and Retriever
> changes tomorrow evening. I'd like to begin the cleanup of loose ends
> and bugs created in those classes by the many changes with the
> database rewrites.
OK, I'll wait until then to backport these changes. This leads me
to my next question. Will it be feasible to "cvs merge" most of my
changes to htdig-3-1-x into htdig-3-2-x, or will this mostly need to be
done manually? I know some stuff, e.g. changes to attrs.html, needs to
be manually added into defaults.cc in 3.2, but what about stuff where
the codebase is similar enough? Would a merge at this stage be asking
for trouble, or would it mostly work out fine? If it'd be a bother,
I can probably fairly quickly go over my 3.1.4 changes and commit them
to 3.2.0b1 as well.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
