From: Andreas Unterkircher <unki@netshadow.at>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Differentiating between http downloads and interactive
Date: Sat, 22 Oct 2005 09:22:25 +0000 [thread overview]
Message-ID: <435A04D1.2080904@netshadow.at> (raw)
In-Reply-To: <C2DA8EC72BEE0740BC5C7F5E04D4EB5160503A@holly.mtech.gg>
I don't know how you really can differ between them. But I guess easy
way would be using HTB burst.
So the first (small?) packets get a high bandwidth immediately trough
burst settings. If more data is requested,
it will be slown down to defined ceil bandwidth.
Cheers,
Andreas
Paul J. Smith wrote:
> Hi,
>
> I’ve been wondering if anyone has thought of a way to differentiate
> between an established http download and interactive http traffic? I
> would like to give interactive http traffic priority over someone
> downloading large files.
>
> Has anyone any ideas how to detect packets that are part of a download
> like this?
>
> Thanks.
>
>------------------------------------------------------------------------
>
>_______________________________________________
>LARTC mailing list
>LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-10-22 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 9:17 [LARTC] Differentiating between http downloads and interactive Paul J. Smith
2005-10-22 9:22 ` Andreas Unterkircher [this message]
2005-10-22 15:23 ` BUCHMULLER Norbert
2005-10-23 3:31 ` Grant Taylor
2005-11-02 16:22 ` [LARTC] Differentiating between http downloads and LinuXKiD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=435A04D1.2080904@netshadow.at \
--to=unki@netshadow.at \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.