On Wed, 13 Oct 2004, Tim Potter wrote:

> On Wed, Oct 13, 2004 at 10:28:39AM +0200, David Barth wrote:
> > Michael : I'm still not sure to see the advantages : you loose type
> > checking/safety usually enforced by compilers when calling a function
> > and you need to duplicate (possibly autogenerated code) for decoding the
> > new DCE_PIPE protocol ? Now, Perl is not really about type safety, so I
> > loose a point... ;-)
> >
> > I'm taking a look at Samba4 libraries, with the help of Richard Renard.

> You might want to look at what I have been working on in the Samba 4
> scripting/swig directory. There's a README which tells you how to
> get things working.
> It implements Python bindings for a subset of the DCERPC client library
> routines. Sorry, no Perl bindings at the moment though.

Hmm, in principle, it should be possible to generate bindings for Perl as
well, I thought, and maybe Tcl ... however ...

A big question is: Do we want to create yet another API. It would seem
possible to port existing Windows code if the Windows API were made
available as a (possibly) thin wrapper on top of the DCERPC client library

Richard Sharpe, rsharpe[at]richardsharpe.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com