Jon wrote regarding 'Re: [SLE] ftp and ftp-data, drifting slightly OT' on Fri, Nov 19 at 00:30:
On Thu, 18 Nov, 2004 at 10:33:38 -0600, Danny Sauer wrote: <snip>
How do you think all of the images on web pages are downloaded, let alone the other media files (pdf, flash, etc)?
http is a nice, simple protocol that also supports handy stuff like [...] Speaking of network POVs:
Suppose I have a router doing priority queueing based on ToS flags (wondershaper). Am I understanding this correct, in that file transfers by way of http are going to end up in the same queue as the 'ordinary' webtraffic?
And if so, then what might one do about it?
Because it seems to me that clients using http for tranfers would then be 'jumping' the queue, so to speak, unless there is some pratical way to differentiate...
Yes, wondershaper works at the transport level - it only knows that the traffic is TCP/UDP/etc, and what port the TCP traffic's destined for, etc. It doesn't know or care what's going on at the protocol level, where things like the mime type, etc are available. If you want to choke down certain types of downloads, you need to use a proxy (probably squid). You can throttle bandwidth from there, using things like the content type and content length to determine how much of the http bandwidth a particular request will be allowed to use. With just wondershaper, people using http are technicaly bypassing the "download" queue. --Danny