dix and Xprint

[Eamon Walsh]

Adam Jackson wrote:
> On Wed, 2008-03-12 at 10:59 +1100, Drew Parsons wrote:
>   
>> Finally, about requestingClient itself, it's only used to obtain a print
>> context via XpGetPrintContext(requestingClient).  Is there any other API
>> to get the identity of the client making a request, other than
>> requestingClient?  If there were, we could potentially clear out these
>> xprintisms from dix completely with just a handful of changes in
>> xprint/ps (well, there'd still be the usage in dixfont.c to think
>> about).
>>     
>
> Probably the right way to do this now is to hook yourself into the
> XaceHookDispatch() call chain during XpExtensionInit(), and stash the
> current client aside in a field in the XpScreenRec (or in some bit of
> global server state really).
>
> - ajax
>   

Maybe this is a dumb question, but isn't the right way to get the 
requesting client simply to look at the "client" argument that gets 
passed in to the protocol dispatch function?  Where is it getting lost here?



-- 
Eamon Walsh <ewalsh at tycho.nsa.gov>
National Security Agency