libmsrpc for Samba 3

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Nicholls wrote:

| I normally have the same preference, but I can see
| there being functions  that will need more than 5
| parameters, some of them inputs and some of
| them outputs.  I like the control block style
| mostly because it consolidates the outputs and there
| will definately be some functions that have multiple
| outputs.
|
| Perhaps something else that should be considered
| is exactly how many functions will have that many parameters
| relative to the functions that only have 1-5 parameters.
| Control blocks seem well suited for functions
| that have many parameters but  might be a bit much for
| functions that only have 2 or 3 for example.  In the case
| of libmsrpc, I think all the functions will have at
| least 2 paramaters (a server handle plus some input).

I guess the point I am (apparently badly) trying to make
is that this is not an all or none decision.  Use control
blocks to consoldate some parameters.  Or all in to one
like Samba 4 does.  Even the Win32 API uses control blocks
like this.  It's the request-reply-in-one-structure that I'm
sort of opposing.

But like I also said before, you're the coder here.






cheers, jerry
=====================================================================
Alleviating the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"I never saved anything for the swim back."     Ethan Hawk in Gattaca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC3ohuIR7qMdg1EfYRAjzDAJ95zV0ckBru+IhysSsPGqgklg+4vACeONHR
SWP1rYDS1SnujEOsyx/X26M=
=B+T1
-----END PGP SIGNATURE-----