We're thinking of using htdig as part of a larger web application
that we'll deliver to a customer. Ideally, the customer will
never need to know anything about htdig -- it will just routinely
dig, merge, and search tens of thousands of pages, for years,
with no administration except the occassional server
restart. Well, that's the ideal. It raises several questions.
(a) How much administration does htdig typically require, after
intitial setup and testing?
(b) What about its databases? Do they ever become corrupt, for
example, when the server crashes during a merge? Do they ever
need rebuilding from scratch? What administration tools are there
to examine, validate, and repair these databases? (I don't see
any documented on the website, which is either a good sign or a
scary sign.)
(c) Obviously, htdig gets embedded in web applications. But has
anyone ever used it in a turnkey application delivered to
customers who are not savvy in administering websites?
(d) What configuration and use practices are recommended and
or cautioned against, for this kind of purpose?
Thanks!
Russell
_______________________________________________
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
