At 6:55 PM -0500 12/3/99, Tom Metro wrote:
>As noted previously, I thought installation and setup was fairly easy,
>but would be greatly improved by having a "quick start" document that
>carried the user from build through cron entries. And the addition of
>some reporting or logging facilities so the operator could get a feel
>for how well the indexing worked.
The "reporting and logging facilites" are there, in the -s and -v options.
Yes, a "quick start" document would be very useful, but it's often
hard for us developers to write such a thing--I know I've forgotten
places where people might get stuck and need help.
>better served by other tools. Of course if efficiency and scalability
>occurs as a side effect of general code improvements, then wonderful,
>but is it worth adding a lot of complication, as for example, a
>threaded version might? It may not best serve Ht://Dig's core
>audience.
Yes, this is a good point. It would take some serious work to make
the current code threaded. However, users pushing the limits can
often point to performance problems a lot easier than those of us
towards the middle of the curve. So it's important to us to know how
changes affect them--they can point the way to code that needs
improvement.
It probably doesn't hurt to mention that the people indexing a lot of
sites are willing to pay for certain improvements as well.
>This was just a thought. I'm new to Ht://Dig, so I don't know whether
>it fits with its philosophy.
I don't know if there's a rigorous "philosophy," but yes, this basically fits.
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
