Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Input Extension documentation
Message-ID: <8907211202.AA04664@expire.lcs.mit.edu>
Date: 21 Jul 89 12:02:45 GMT
References: <301@remo.atexnet.UUCP>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 21


    I do have a document called "X11 Server Extensions" from 1987 but it
    doesn't seem to be complete.

Yup.

    In particular, it doesn't define a standard interface through which
    an extension can send an event to a client.

In the MIT server, the basic interface is WriteEventsToClient.

    But I'm worried that I'll do this in a non-standard way that will only
    work with the MIT dix layer.

At this point, there really isn't such a thing as a standard internal server
interface for extension portability.  The document you cite is an attempt at
one, which was done before there were very many extensions implemented.  It
still isn't clear there is enough commonality among server implementations to
permit a reasonable common interface.  (For example, some of the interfaces
in the MIT servers are changing in R4, partly to provide better support for
extensions.)