Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!morgan.COM!jordan
From: jordan@morgan.COM (Jordan Hayes)
Newsgroups: comp.windows.x
Subject: Re: printing at X terminals
Message-ID: <9007222107.AA26600@s6.Morgan.COM>
Date: 22 Jul 90 21:07:44 GMT
References: <9007192115.AA24166@expire.lcs.mit.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: Morgan Stanley, & Co., Inc. / New York City, NY
Lines: 25

Robert Scheifler <rws@EXPO.LCS.MIT.EDU> writes:

	I certainly want to be able to sit at home with my X terminal,
	using the machines at the office, and still be able to print
	files on the printer sitting next to my X terminal, which is
	connected to the serial port.  I just don't want to use an X
	extension to print it.

Ah-hah!  But, that serial port that connects you to your office doesn't
speak a general transport protocol, but rather a proprietary protocol
especially developed to do compression of the X protocol (admitedly not
designed for low-bandwidth environments) over your slow modem -- so all
there is is an X stream, no room for anything else.

I agree, it doesn't belong there.  But what the heck? ;-)  Unless you
want me to run two modems to the office, one for the dedicated X
stream, and one for a general purpose transport protocol link,
something needs to get sacrificed.  For the ethernet environment, where
the X stream is already coming in via an general transport, the vendor
has no business hacking that into the X protocol ...

# "Do you want protocols that look nice, or protocols that work nice?"
#	-- mike padilipsky

/jordan