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@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
