libmsrpc for Samba 3

[Chris Nicholls]

Gerald (Jerry) Carter wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Chris Nicholls wrote:
>
>  
>
>>I'll add the the rpc_includes.h and rpc_proto.h, along 
>>with the quick and dirty makefile to the source/libmsrpc/
>>directory for the moment and get that commited to svn tonight
>>once I widdle down the headers a bit.
>>    
>>
>
>The svn issues should be clread up for you.  I'm checking
>with metze on whether this was the proper solution since
>it will affect other developers in the soc group as well.
>
>  
>
>>As for the interface I'll have to put a bit more thought 
>>into it. I think the current interface is ok for the moment
>>but I figure once I get a little deeper into it i'll
>>have some good ideas.
>>    
>>
>
>I'd suggest look at the Win32 API here (never thought I
>would say that).  The registry API is given here:
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/registry_functions.asp
>
>I'm not saying this is perfect by any means (it's down right
>horrible in some places), but we should know the related work
>before writing a new one.
>
>
>  
>
I'm thinking that modelling the client interface in a similar way to the 
MSDN api is probably the way to go, at the very least for winreg and 
lsarpc, as the functions seem to parallel the possible operations on 
those pipes.  I may be wrong but it seems like at least 
rpc_client/cli_lsarpc.c is modelled after this as well.  For other pipes 
that might not have an API that parallels with it (I'm not sure what 
wkssvc would be under) using the current rpc_client interface along with 
the possible operations on the pipe would be a good guide.

I think the next step should be hammering out the details of how  a 
server handle will operate. Any objections?

Also, I haven't seen much information around regarding the spoolss pipe. 
Do you know of any good reference material? If not I'll try to learn as 
much as I can from ethereal captures.

Chris

>
>
>
>
>cheers, jerry
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.0 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>iD8DBQFCzTjnIR7qMdg1EfYRAkMXAJ9KAyrgogEXBEclhZmEbd19bnEVhACg5/2y
>00P81cbCsbC8Tjtp29angU4=
>=d4Hi
>-----END PGP SIGNATURE-----
>
>  
>