At 8:39 AM +1000 4/11/01, Brian White wrote:
>We selected ht://Dig to go on a clients internal site, and have been
>happy enough with it so far, with the exception of logging - I ended
>up modifying the code to get around what were for us limitations.
>I'd like to describe the changes I made - I would be curious to get
>some feedback.
I put in the current logging code as a horrible (but workable) hack.
Since syslog handles locking for you, it seemed like a decent
possibility.
>2) The format that the logged information is written out as is a
>total pain to pick information out of
A lot of people have complained about this, so alternative
suggestions are most welcome. If there's a way to do a
user-configurable format that doesn't incur speed penalties, this
might be nice too.
>3) The logging information is written out every time htsearch is called.
Yes, this is a pain.
>I then added
> <input type=hidden name=init value="Y" >
This doesn't seem necessary. Shouldn't you just check whether the
user has requested page 1?
> Apr 9 09:38:43 myhost htsearch[11228]: 192.168.1.10 [myconfig] (and) [car]
> [(car or auto or automobile)] (98/10) - 1 --
>http://mywebhost.com.au/search/search.html
>number of seconds since epoch at the front:
> 986844235|192.168.1.10|myconfig|and|car|(car or auto or
>automobile)|98|10|1|http://mywebhost.com.au/search/search.html
I don't know about most people, but I would probably go with the
standard date format rather than the seconds since epoch.
Still, I think this is a great contribution--could you send the patch?
Thanks,
--
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
