On Fri, Oct 2, 2009 at 2:04 PM, Philip A. Prindeville <[email protected]> wrote: > Hi. > > I haven't contributed to Apache in about 10 years, so it's been a while > since I've stared at the source. > > I did, however, recently pull down the 2.2.13 tarball and did: > > [phil...@builder ~/httpd-2.2.13]$ find . -type f -print | xargs grep IP_TOS > [phil...@builder ~/httpd-2.2.13]$ > > > Hmmm. Any reason that HTTP traffic wouldn't be QoS marked so that it > can be handled properly? > > (Assuming that we have or will have net-neutrality... ;-) ) > > I just don't want software updates (which aren't time critical but *do* > suck down huge amounts of bandwidth) degrading my VoIP service... > > Seems reasonable, right? > > Of course, we could mark all open sockets as AF11 (for instance)... but > then if you have a cgi plugin generating video, it would have to > re-setsockopt() the socket to remark the traffic appropriately... Is > that overly burdensome? Or reasonable?
A patch to configure it at runtime (maybe per-directory?) would be a reasonable thing to include. Wouldn't be that bad, just a request output filter that set the socket opt and then removed itself.
