Shantonu Sen (firstname.lastname@example.org)
Tue, 30 Mar 1999 12:39:04 -0500 (EST)
well, you could be really, really specific and have separate inputs in
named "from-month" "from-day" "from-year" "to-month" "to-day" "to-year",
and then there would be no misinterpratation. i wouldn't imagine that this
would make the GET URL too big.
the other question is whether to reprogram htsearch to accept these
parameters, or have it accept a general date parameter DDMMYYYY and depend
on wrapper scripts to massage whatever users enter into an appropriate
format. it strikes me that wrapper scripts in general would give engine
administrators more flexibility, because you could have users enter dates
in standardized format (at least according to them) and translate to what
htsearch understands. so if a particular adminstrator wants to enter
"January 15, 1999", the wrapper script would parse this into 150199.
On Tue, 30 Mar 1999, Geoff Hutchison wrote:
> On Mon, 29 Mar 1999 email@example.com wrote:
> > Doesn't the HTTP header give you the file modification date? And I
> > sure hope it's in the format YYYY so it will work next year, too ;-)
> No, that's not the problem. We already get the date of the documents from
> the HTTP header. The problem is how you get the date from the *search
> form* since the most obvious solution (a text field for users to input a
> date) requires working out the date format.
> So my question is this: do we just limit the format? If so, what do we
> use? If not, how do we figure out the format used?
> -Geoff Hutchison
> Williams Students Online
> To unsubscribe from the htdig mailing list, send a message to
> firstname.lastname@example.org containing the single word "unsubscribe" in
> the SUBJECT of the message.
To unsubscribe from the htdig mailing list, send a message to
email@example.com containing the single word "unsubscribe" in
the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Tue Mar 30 1999 - 11:37:37 PST