[standards-jig] JEP 65 - Bytestreams

Dave Smith dizzyd at jabber.org
Thu Dec 19 17:47:01 UTC 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Thursday, Dec 19, 2002, at 07:44 America/Denver, Jan Niehusmann 
wrote:

> On Thu, Dec 19, 2002 at 07:25:31AM -0700, Dave Smith wrote:
>> You know, this scenario of waiting will still happen with JEP 46. If
>> both parties exchange IPs that are fully NAT'd, neither party will be
>> able to connect and you get the dreaded "1m" delay. Having both 
>> parties
>> attempt to connect to each other in no way solves the possibility of a
>> long connect sequence.
>
> Well yes, but people understand if the computer tries connecting for 1m
> and then says 'Sorry, this is not possible'.
>
> But if the transfer does work after waiting 1m, and that delay occurs
> for every single connection, people get annoyed. And in my experience,
> most of them will blame such delays to 'slow networks', and won't look
> for some 'I am behind a firewall' configuration.

Let me say this again...

<rant>

It is the responsibility of the APPLICATION to ensure the user does not 
get annoyed with "slow networks"

There is NOTHING you can do at the protocol level to attain this 
(mythical) goal of ensuring the TCP connection doesn't take a long time!

JEP-46 does not inherently provide any mechanism for ensuring the TCP 
connection sets up quickly; nor does JEP-65.

NO JEP THAT WE WRITE CAN PROVIDE ANY GUARANTEE AROUND HOW LONG A USER 
WILL WAIT FOR A CONNECTION TO BE ESTABLISHED.
NO JEP THAT WE WRITE CAN PROVIDE ANY GUARANTEE AROUND HOW LONG A USER 
WILL WAIT FOR A CONNECTION TO BE ESTABLISHED.
NO JEP THAT WE WRITE CAN PROVIDE ANY GUARANTEE AROUND HOW LONG A USER 
WILL WAIT FOR A CONNECTION TO BE ESTABLISHED.

However, JEP-65 DOES provide an orderly framework for establishing 
connections. JEP-46 does NOT. Arguments around how long a connection 
takes to get going are POINTLESS.

</rant>

:)

Diz

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0 (Build 349) Beta

iQA/AwUBPgIGHmDRN3IVRx7DEQIyKgCeNwxPwv80Y7+yV1VnmdXCR9/4Sv8AoNSy
dIghsi790zAtIsrv6loYqXSn
=Yvcp
-----END PGP SIGNATURE-----




More information about the Standards mailing list