Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!lll-lcc!ames!ucbcad!ucbvax!decvax!tektronix!teklds!hercules!glennw
From: glennw@hercules.UUCP
Newsgroups: comp.windows.x
Subject: Re: XUpdateMouse()
Message-ID: <1787@hercules.TEK.COM>
Date: Thu, 26-Feb-87 10:35:47 EST
Article-I.D.: hercules.1787
Posted: Thu Feb 26 10:35:47 1987
Date-Received: Sun, 1-Mar-87 08:15:44 EST
References: <8702231839.AA02342@ingres.Berkeley.EDU>
Organization: Tektronix Inc., Beaverton, Or.
Lines: 11
Summary: issue with X architecture


   Recently I heard a presentation from a workstation supplier on its
plan to support X.  They plan to provide an optimized Xlib that uses
shared memory instead of IPC when talking locally to their own server.
Having just suggested a user extension to Xlib, I am concerned that any
re-architecture of the Xlib/server interface like this must permit user
extensions to the Xlib to be used in conjunction with the re-architected
interface.  Otherwise, people should be warned to avoid any non-standard,
non-Xlib interface to the protocol.
-- 
Glenn Widener