Laurens M. Fridael said: > I was thinking of maintaining a simple "registry" (just an XML file on a > web server) that specifies sites/servers where you have to be extra > careful. This way JPluck (or any other parser) can automatically lower > the connection count if it is set too high by the user, or introduce a > delay. A parser fetches this registry periodically to refresh its local > copy. >
This would be good unless your site goes down. And if Jpluck configured to lookup at this site bt default, what if you plan to use Jpluck in a situation where it's not on the internet. A better solution would be to have an option in the site config. If you want a registery for sites to be careful on, then make it like a repository for xml configs. Kinda like the showcase in PluckerDesktop. >>> As an aside: do people think the default user-agent should be >>> AvantGo? >> >> No, because we aren't AvantGo. >> >> They already do, see my original reason for including the UserAgent >> and Referer headers and parser options in the Python parser. > > So that is actually a reason to default to AvantGo? > I'm gonna think that the option to select it on special occations where masking is necessay is good. But for the larger part, we want visibility that Plucker or other 'parsers' exist. So these places realize there is more out there than just Avantgo and are more inclined to support us better. How can you go to a site and tell them you want them to better support you in some fashion when they see no evidence in their log files that anyone other than avantgo pulls the data? They will think you are an even more of a minority than you actually are. --Wes _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
