Re: JPluck 0.9 prerelease 2

[Edward Rayl]

David A. Desrosiers wrote:

	I understand your needs are different, but the design approach needs
to be local, and self-contained, not centralized on a server. Remember, the
design of Plucker keeps the CLIENT in control, not the server.
  

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.
    

	Ick. If I set or override a parameter, I EXPECT it to stay
overridden, and not reverted by some tool I can't control upstream.

  

A parser fetches this registry periodically to refresh its local copy.
    

	As an option, defaulted to off, and enabled by the user, perhaps.

I agree with David on this one!  I would want to control this as a user, otherwise I _will_ be taking a look at your source code ;-)