Feature Requests item #2915224, was opened at 2009-12-15 18:15
Message generated for change (Tracker Item Submitted) made by pprindeville
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2915224&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libcurl
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Philip Prindeville (pprindeville)
Assigned to: Daniel Stenberg (bagder)
Summary: Site-wide defaults needed for libcurl

Initial Comment:
Feature 2914924 entails adding QoS support for curl and libcurl. This exposes the following deficiency in curl:

Hard-coding QoS settings into libcurl is Draconian, and mostly broken, since (a) many sites will want to hand-tune their QoS settings on a per-protocol basis, and (b) still other sites won't want to deploy QoS at all because of legacy routers that don't understand RFC-2474 and later.

Further, using per-user options to deploy QoS represents a major trust obstacle, since users generally act in their own interests and not in a cooperative, collaborative, or altruistic way. It's also difficult to add new defaults to the existing profiles of dozens or even hundreds of users... but it's much easier to edit a single system-wide defaults file.

One might even argue that some defaults should *only* be exposed at a system-wide level, and not be settable at a per-user level (such as the forced use of an HTTP or Socks proxy... or in this case, QoS tagging).

The lack of such granularity (and partitioning) of control could be a blocker for feature 2914924.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2915224&group_id=976
Received on 2009-12-16