Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!decwrl!oli-stl!asylum!karl
From: karl@asylum.SF.CA.US (Karl Auerbach)
Newsgroups: comp.protocols.iso
Subject: Re: X-WINDOWS & OSI
Message-ID: <2639@asylum.SF.CA.US>
Date: 25 Jun 89 07:27:35 GMT
References: <5560025@hpindda.HP.COM> <99600003@p.cs.uiuc.edu>
Reply-To: karl@asylum.UUCP (Karl Auerbach)
Organization: The Asylum; Belmont, CA
Lines: 18

In article <99600003@p.cs.uiuc.edu> zweig@p.cs.uiuc.edu writes:
>
>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.

Real ASN.1 encoding and decoding is not a null function.  Unless you make
some serious restrictions, it can be a real CPU burner -- not just at
the start end end of the session, but for every byte transferred.

Are you suggesting going half way and doing ACSE but not a real ASN.1
revision of X?  

>   Rule 1: Don't believe everything you read.

I didn't.

					--karl--