From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to limit per tcp session ?
Date: Fri, 18 Jun 2004 00:07:50 +0000 [thread overview]
Message-ID: <40D23256.1030400@dsl.pipex.com> (raw)
In-Reply-To: <200406161632.43708.rio@martin.mu>
Rio Martin wrote:
> I'm so surprised with all reply from the list. I thought someone has figured
> it out how :))
>
> Okay, then let me describe whats on my mind to help develope this project (if
> someone dare to start make a project)
>
> The idea perhaps like this:
> Let say i'm goin to download some graphics from www.lartc.org. The first
> session i opened my browser, created connection localhost:3101 -->
> www.lartc.org:80, the 2nd, localhost:3102 --> www.lartc.org:80, and so on.
> So as you could see, this is the key. Source port, not Destination port.
> Every time you open new window of your browser and connect to some host, they
> create other originating port which is completely different from the 1st.
How many concurrent tcp connections per page depends on the browser and
server settings - both tweakable, so you would get different speeds
depending on site/browser combination.
Why do you need to do per tcp? There may be a better way to solve your
problem.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-06-18 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 9:32 [LARTC] How to limit per tcp session ? Rio Martin
2004-06-16 12:24 ` Ed Wildgoose
2004-06-16 18:51 ` Bill Denney
2004-06-17 5:59 ` Rio Martin
2004-06-17 7:22 ` Ed Wildgoose
2004-06-18 0:07 ` Andy Furniss [this message]
2004-06-18 0:10 ` Andy Furniss
2004-06-18 1:56 ` Bill Denney
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=40D23256.1030400@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.