David A. Desrosiers said:
> > Isn't this going to greatly increase the bandwidth used by the sitescooper
> > site if it has to deliver this information every time someone runs
> > sitescooper? Or is that an issue for you?
>
> Not to mention... what if the site hosting that .site file
> is down?
These are the solutions to that problem I've come up with:
1. instead of the users directly connecting to each .site-file host,
sitescooper.org has a cron job which gets the timestamp on the file once
a day and assembles an index.
2. sitescooper (at most once a day) connects to sitescooper.org and gets
the latest index.
3. using its own site files and the index of "latest site files" it can
work out which site files need updating.
4. an alternative index download location can be used (command line
arg?) in case sitescooper.org falls off the face of the net.
_______________________________________________
Sitescooper-talk mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/sitescooper-talk
