According to mike grommet:
> If the user hasn't specified a time range
> Start date should consist of something like
> Jan 1, 1900, and end date should consist of  today's server date.
> 
> One problem that will occur is that the web server returns modification
> dates
> In UTC, and the script we use to generate the pages for indexing will also
> need
> To return times in UTC�  However, the user will specify their dates/times in
> Localtime.  This will only make a difference on a few occasions but could
> provide
> Unexpected search results.  I still have to work this out

The important this to keep in mind here is that the back end and the front
end can be quite independent of each other.  Standards dictate that UNIX
systems keep time in a time_t, which is in UTC, and that HTTP servers give
modification times (and any other dates/times) in UTC, in a specific
string format.  That means your CGI script, if it outputs a Last-Modified
header, must use this same format and UTC.

The front end is a whole other matter.  Currently, htsearch uses localtime()
to convert the time_t format modification dates of matched documents, so it
reports these in the htsearch server's local time zone.  For consistency,
it would make sense to use this same time zone for your date conversions.
If you want htsearch to run in a different time zone than that of the
HTTP server on which it's hosted, you can use a wrapper script that changes
the TZ variable.  This would work on most UNIX systems.

> How do I keep the date requirements when viewing multiple pages of results

That's what Display::createURL() is for.  Make sure your parameters get
propagated there, just like all the other ones.  They also must be propagated
to the follow-up search forms (installdir/*.html), via setVariables().

-- 
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] containing the single word "unsubscribe" in
the SUBJECT of the message.

Reply via email to