Joerg Sommer <[EMAIL PROTECTED]> writes:
> Andrew M. Bishop <[EMAIL PROTECTED]> wrote:
> > Joerg Sommer <[EMAIL PROTECTED]> writes:
> >
> >> does wwwoffle set the ip TOS flag? Maybe is 'Minimize monetary cost' set
> >> while fetching or 'Maximize throughput' for ftp (as requested in RFC
> >> 1349) set?
> >
> > There are no TOS options set in WWWOFFLE for any of the types of
> > connection that it makes.
> >
> > It is difficult to know which of the TOS options would be the best one
> > for WWWOFFLE to use:
> I didn't find any definition how the TOS flags should be used with http
> and I don't have any idea which flag to use. But there is a definition
> for ftp in the RFC 1349.
The definition in RFC 1349 is actually just a copy of a table from
RFC 1060 which is obsoleted by RFC 1340 which is obsoleted by RFC 1700
which is obsoleted by an online reference (see RFC 3232).
What is actually said in RFC 1700 is:
-------------------- RFC 1700 --------------------
Generally, protocols which are involved in direct interaction with a
human should select low delay, while data transfers which may involve
large blocks of data are need high throughput. Finally, high reliability
is most important for datagram-based Internet management functions.
...
The following are recommended values for TOS:
...
FTP
Control 1000 (minimize delay)
Data (2) 0100 (maximize throughput)
-------------------- RFC 1700 --------------------
>From this is would seem that HTTP could be low delay or high
throughput since they may interact with the user and may have large
blocks of data.
> But you can control with this flags, what traffic is preferred before some
> other - this is traffic control/shaping. The linux kernel routes by
> default traffic with the minimize delay flag faster than normal and
> normal faster than maximize throughput or minimize cost traffic. Because
> this I think you can control if the traffic of the fetch process blocks
> the normal traffic at going online.
>
> I often fetch many pages at going online, so my connection is unusable
> for normal browsing. If the fetch process would set the minimize montary
> cost flag the normal traffic would be preferred before the "fetch" traffic.
You cannot control the data that is sent to you by the server, only
the data that you send. This means that the only thing that could be
delayed for the fetch requests is the acknowledgements, but there are
a lot fewer of these.
The speed of a dial-up connection is typically only a few (4-6)
packets per second from the server. Trying to make many more
connections than this will always introduce long delays. It doesn't
matter what flags you set the bandwidth cannot be increased.
If you slow down some of the traffic from WWWOFFLE to allow others
through faster then you are more likely to have timeouts. You could
increase the WWWOFFLE timeout, but you could aternatively decrease the
number of fetch processes that run at the same time.
> Because wwwoffle does also support ftp and for ftp a usage of the TOS
> flags is defined, wwwoffle should at least support this.
It is recommended, not defined as a requirement.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.8/user.html
