Neil Bothwick was saying..
> > This isn't possible.
:-( Shame!
> > data arrives at whatever speed the sending server and intervening
> > connections can handle, it's not possible to prioritise.
Ah, but when you have a modem connection, there is a massive
bottleneck in the modem's download speed. Obviously, if the data
isn't actually coming from the remote server as fast as you'd like its
just tough luck, but when data *is* available from various sources,
you can have preference about which one you'd like first. It's just a
question of whether it's actually possible to do anything about this
preference.
But then Holger Rabbach said..
> Well, it's not impossible to do this -
> "maximum bandwidth used" by the tool. It achieves this apparently by
> simply delaying packet acks in a smart way to keep the server from
Hm. So if I understand correctly what you are saying, in theory you
could achieve it like this: Each application could specify a dynamic
"priority" per connection to the TCP/IP stack. Then the stack could
send Ack's for connections with a high priority until the incoming
data flow dropped off because the server for those connection(s)
wasn't responding quickly enough. It could then send out Ack's for
lower priority connections, and so on. It wouldn't be quite ideal,
but it might "encourage" the desired trend for the right packets.
Would that work?
I have a nasty suspicion though, that this kind of modification to the
existing Genesis code would be a huge amount of work to implement?
Although I still think it would be a good idea. :)
Cheers,
Ian
===
--
http://www.greew.freeserve.co.uk
--
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
