Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: adding extension events
Message-ID: <8910241320.AA03659@expire.lcs.mit.edu>
Date: 24 Oct 89 13:20:39 GMT
References: <7009@ingr.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 15


    It seems
    that the machinery to generate unique masks for extension events is
    already in place, but there's no way to tell clients what those
    generated masks are. 

    What am I missing?

Nothing.  Yes there is code in the sample server, but no there isn't
any general mechanism for exporting such events in the core protocol.

In general, extension definers have decided against trying to use
the same event mask as the core protocol (partly because there are
so few bits remaining), and just define their own selection mechanism
as part of the extension.