[SAMBA-TNG] using and createing libsmb and libmsrpc

[Cole, Timothy D.]

> -----Original Message-----
> From:	Luke Kenneth Casson Leighton [SMTP:lkcl at samba.org]
> Sent:	Wednesday, January 19, 2000 12:55
> To:	Multiple recipients of list SAMBA-NTDOM
> Subject:	RE: [SAMBA-TNG] using and createing libsmb and libmsrpc
> 
> On Thu, 20 Jan 2000, Mayers, P J wrote:
> 
> > Well, I'm kind of assuming that if Luke makes changes to libmsrpc, he's
> not
> > going to change the application level interface (I hope), or he's going
> to
> > use some kind of interface versioning (struct dwSize members for
> example).
> 
> hey guys, you'll have to clue me in here, i have no idea what you're
> talking about!
> 
	Basically he's talking about different ways of handling binary
compatibility across library versions.  Among them, either keeping a
consistent API, or using opaque structures, and passing the size/desired
size to all functions that work with them.

> is ./ in the lib path?  because that's what i expect, for now: libraries
> to be loaded from the cwd, at least until the libraries stabilise.
> 
	This is dependent on the system configuration, but the library
search path (much like the executable search path) should not normally
include ./, for security reasons.

	The LD_LIBRARY_PATH environment variable (on amost all POSIX systems
I'm aware of) specifies the shared library search path -- appending the
installation directory to it from a wrapper shell script is the normal way
of dealing with this.  (c.f. Mozilla, et al)

> btw, _yes_ i intend to to a total replacement of the libsmrpc code, with
> function parameter arguments EXACTLY the same as the MSDN.  this will be
> about.........hmmm.... four to six weeks' work.
> 
	What specific benefits are there to duplicating that hideous
interface?  I mean, seriously?