Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Extension Bugs
Message-ID: <8905301156.AA03727@expire.lcs.mit.edu>
Date: 30 May 89 11:56:43 GMT
References: <26900067@m.cs.uiuc.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 9

The documentation in doc/Server/ext.doc is incorrect.

In the case of replies, it is up to the extension to do the swapping.
The top-level ReplySwapVector is only for swapping major-code requests.
Extension requests are indexed by some minor code, and their reply swappers
cannot be stored in this table.

Extensions have been written using both of these routines.  Most extension
writers probably use the source rather than the documentation.