dce/rpc "client" api

[Luke Kenneth Casson Leighton]

john,

one of the things that i started in cliffs was the removal of all global
variables, hiding them behind "handles".

this would make it much easier to multi-thread samba, and would also make
it clearer as to which portions of globals are required by which services.



> However that has side effects that would cause a major rewrite of the source
> code, as effectively I would be making the code multithreaded.
> 
> Basically to prevent blocking threads, I would have to have each routine
> that does any I/O call schedule a followup routine and then return while the
> I/O completes in the background.  Also all thread global variables would
> have to be tracked in one malloc() structure.
> 
> I bring these points up, because there may be some benefit from looking at
> how to implement this from a UNIX perspective.
> 
> Putting the thread global variables in their own structure (if they are not
> already there) can make the source code easier to follow, even in a program
> structure that depends on using fork().
> 
> -John
> wb8tyw at qsl.network
> 
>