97 lines
3.0 KiB
Plaintext
97 lines
3.0 KiB
Plaintext
From: asang at yahoo.com (Asang Dani)
|
|
Date: Mon, 24 May 1999 18:44:52 GMT
|
|
Subject: win32netapi module -version 1.0beta1 (on Windows NT4/5)
|
|
References: <mt2.0-24223-927475576@news.informatik.uni-bonn.de> <7ibdu5$bhe$1@m2.c2.telstra-mm.net.au>
|
|
Message-ID: <7ic6n4$cjv$1@nnrp1.deja.com>
|
|
Content-Length: 2667
|
|
X-UID: 1847
|
|
|
|
hi Mark,
|
|
|
|
It really looks quite similar. I looked at your *win32net* module and
|
|
found that some of the interfaces are not present in your module, but
|
|
are part of *win32netapi* (my module).
|
|
|
|
1. NetLocalGroupDelMembers
|
|
2. NetWkstaUserEnum
|
|
3. NetWkstaGetInfo
|
|
4. NetWkstaSetInfo
|
|
5. NetWkstaTRansportAdd
|
|
6. NetWkstaTransportEnum
|
|
7. NetServerDiskEnum
|
|
8. NetGroupAddMembers
|
|
9. NetGroupDelMembers
|
|
10. NetShareCheck
|
|
11. NetUseAdd
|
|
12. NetUseDel
|
|
13. NetUseEnum
|
|
14. NetUseGetInfo
|
|
|
|
The only API that is present in *win32net* but not present in my
|
|
module -
|
|
|
|
NetMessageBufferSend.
|
|
|
|
Please correct me if I am wrong about these differences. About the
|
|
info. level param, I think that the info. level numbers in most of
|
|
these APIs are really crazy in base APIs. (101, 102, 1024, 512 ...). So
|
|
I return dictionaries with keys for maximum possible info level
|
|
(constranied by the privileges of user executing the API), in most of
|
|
the cases. It's upto the user to choose which key/values he is
|
|
interested in. I think it is better to free the programmer from the
|
|
burden of remembering which fielss are present in which info. level
|
|
and refer constantly to MSDN to find this info.
|
|
|
|
regards,
|
|
asang..
|
|
|
|
|
|
In article <7ibdu5$bhe$1 at m2.c2.telstra-mm.net.au>,
|
|
"Mark Hammond" <MHammond at skippinet.com.au> wrote:
|
|
> I hate to tell you this, but the Win32 Extensions build 125 and later
|
|
> includes an almost identical interface to this in the win32net module;
|
|
> indeed win32net is arguably better as it allows arbitary "information
|
|
> levels", whereas yours only supports single info levels per data
|
|
structure.
|
|
>
|
|
> The interface is almost identical - except win32net functions take an
|
|
extra
|
|
> integer param which indicates the information level requested/being
|
|
set...
|
|
>
|
|
> Mark.
|
|
>
|
|
> Asang Dani wrote in message ...
|
|
> >hi,
|
|
> > I have written a module win32netapi to provide simplified access
|
|
to
|
|
> >various networking APIs (Net* functions) on windows NT. The module
|
|
can
|
|
> >be downloaded from
|
|
> >
|
|
> > http://members.tripod.com/asangdani/public/
|
|
> >
|
|
> >It includes extensive documentation (html and ASCII) and examples.
|
|
> >
|
|
> >Following are the contents of README included with the release :-
|
|
> >
|
|
> > This python module is inspired by 'Win32::Lanman' module for
|
|
Perl
|
|
> >written by Jens Helberg (jens.helberg at bosch.com). I have made no
|
|
changes
|
|
> >to the basic interface. It's a port from perl XS to python
|
|
extensions. I
|
|
> >have also used SWIG (Simple Wrapper Interface Generator) to simplify
|
|
> >some of the type mappings. SWIG can be freely downloaded from
|
|
> >(http://www.swig.org).
|
|
>
|
|
>
|
|
|
|
|
|
--== Sent via Deja.com http://www.deja.com/ ==--
|
|
---Share what you know. Learn what you don't.---
|
|
|
|
|
|
|
|
|