I agree and the fact is, if it takes a separate database, so be it, much simpler than
trying to mod the code for this. Maybe in the future, it might be a good idea. Maybe
some
sort of web based config interface for all these things. Fact is, the net is not
getting
any smaller and I suspect that those using this seriously will need more functionality.
Mike
>At least IMO, true operational requirements for any such system
>would be quite user-specific. The (full) set of user requirements would tend
>to include:
>
> Scheduling capabilities.
> Varying frequencies, perhaps even within the same URL.
> Inclusion and/or Exclusion of specified nodes, within a url.
> Statistical-recording capabilities.
> Varying underlying-database formats.
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: <http://www.htdig.org/mail/menu.html>
FAQ: <http://www.htdig.org/FAQ.html>
