Path: utzoo!attcan!uunet!jarthur!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!arisia!roo!janssen From: janssen@parc.xerox.com (Bill Janssen) Newsgroups: comp.windows.x Subject: Re: printing at X terminals Message-ID: Date: 23 Jul 90 22:29:31 GMT References: <9007192115.AA24166@expire.lcs.mit.edu> <9007222107.AA26600@s6.Morgan.COM> Sender: news@parc.xerox.com Organization: Xerox PARC, Palo Alto, CA Lines: 20 In-reply-to: jordan@morgan.COM's message of 22 Jul 90 21:07:44 GMT In article <9007222107.AA26600@s6.Morgan.COM> jordan@morgan.COM (Jordan Hayes) writes: [...] so all there is is an X stream, no room for anything else. As I pointed out earlier, there is plenty of room in the X protocol for arbitrary client-to-client sub-protocols. You can do local printing over a pure X stream (no extensions) by adopting some client-to-client conventions. But your comment assumes an X-only stream, rather than a "remote workstation" stream, which would support X as a subset. Why? Lots of people use SLIP as the stream protocol, which allows you to run many task-specific sub-streams on it. Bill -- Bill Janssen janssen@parc.xerox.com (415) 494-4763 Xerox Palo Alto Research Center 3333 Coyote Hill Road, Palo Alto, California 94304