- **status**: open --> closed-duplicate
- **Comment**:

Duplicate of [feature-requests:#44]

---
** [feature-requests:#65] Please add support for setting IP TOS/Precedence flags**
**Status:** closed-duplicate
**Labels:** libcurl 
**Created:** Wed Nov 07, 2012 12:20 PM UTC by Chris Wilson
**Last Updated:** Thu Nov 08, 2012 01:07 PM UTC
**Owner:** Daniel Stenberg
IP TOS \(Precedence\) flags as described in RFC 791 are really useful for building QoS routers that treat bulk and interactive traffic differently; but only if client applications actually bother to declare whether their traffic is bulk or interactive.
SSH and bittorrent do this already, but there doesn't seem to be any way to do it in curl. 
You can do it with setsockopt\(IP\_TOS\) on all platforms that support it except Windows, which disables this functionality and uses DSCP instead \(unlike everyone else\).
Some discussion of whether to use IPTOS\_THROUGHPUT, IPTOS\_PREC\_PRIORITY or something else for bulk traffic: 
http://lists.ibiblio.org/pipermail/bittorrent/2004-December/001060.html . I don't particularly care as long as we do \*something\* to mark bulk and interactive traffic differently.
Please could we add at least a flag that sets the precedence of all connections made by curl to bulk or interactive?
Even better would be heuristics to determine which mode is appropriate. My guess is that all applications of command-line curl are bulk, using libcurl to write to an output file or for any protocol except HTTP is bulk, and everything else \(libcurl HTTP not to a file\) is interactive.
If you accept this proposal I can try to work up a patch.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/feature-requests/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/feature-requests/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.