Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!lll-winken!xanth!mcnc!decvax!crltrx!max.crl.dec.com!jg
From: jg@max.crl.dec.com (Jim Gettys)
Newsgroups: comp.protocols.iso
Subject: Re: X-WINDOWS & OSI
Message-ID: <228@crltrx.crl.dec.com>
Date: 26 Jun 89 17:22:21 GMT
References: <99600003@p.cs.uiuc.edu> <5560025@hpindda.HP.COM>
Sender: news@crltrx.crl.dec.com
Organization: Digital Equipment Corporation, Cambridge Research Laboratory
Lines: 22


> Certainly 2 or 3 seconds of ACSE muddling when I open an x-session (assuming
> a reasonably bad ACSE implementation) isn't going to be noticed, and once
> we're connected the Presentation and Session layers are null.

I don't see how you can justify such a statement under any circumstances.
Are you seriously suggesting that applications should take additional SECONDS
just to get a connection started?????!????!!!???  Not to mention applications
which may want to have multiple connections open.

2-3 seconds delay sure would be noticed on my machine.  Most of the X tools
I use are up in under a second.

Every time you start an application, it has to open a connection to the X server.
This wants to happen fast; acceptable is only when it is less than human
perception; so this sets an upper bound on a local net of 50 milliseconds or
less.  There are other things that need to be done besides connection setup;
you only get a small fraction of the entire budget of time to play with.
This is easy to do under TCP with current workstations.  Adding several
seconds to connection setup is crazy.

					- Jim Gettys