DCOM client support
DCOM client support finally works! TODO things left for DCOM now are:
- Server side support
- Supporting base interfaces outside current file
- Fix annoying bug in pidl WRT to IStream_Read
- Implement IUnknown
- Implement pinging
DCOM client support finally works! TODO things left for DCOM now are:
It seems the list is getting longer rather then shorter…
Now that I’ve been working with MSRPC extensively for some time, I’m actually starting to like it ! Although things could’ve been less complex (NDR alignment, for example) the protocol itself is actually quite clean and nicely set up.
Some of the major flaws in MSRPC are (imho):
One of the nice things about RPC (and perhaps also one of it’s problems) is it’s flexibility. The encoding can be changed as well as the transport that’s being used.
LinuxReviews has interviewed my fellow BitlBee developers and me. Interview available here.
(Update 16:55) Slashdot has a post about the interview as well.
Finally, the rewrite of the registry subsystem in Samba 4 is starting to finish off. I changed some major things after the initial version:
Now that the last few bugs in the win32 version of Bitlbee have been fixed, I have brought up a public test server. Point your IRC client at win32.bitlbee.org:6667 and try it!
The test server is running the 9 Sept snapshot on NT4 inside of VMware.
Stefan Weichinger has used the samba-docs build system for the documentation of AMANDA, The Advanced Maryland Automatic Network Disk Archiver.
Preview is available here. Very neat stuff!
Ctrlproxy is discussed in two hacks in the upcoming O’Reilly title IRC Hacks, edited by Paul Mutton. Both articles were written by Wilmer van der Gaast.
I have been using CVS to store my source code and documents for the past couple of years. CVS works quite well, because it makes synching data between various computers easier, doesn’t require you to make a backup of your files every time they change and makes it easier to work on a project together with others.
However, CVS has its glitches. Renaming/moving files isn’t really handled - there is no notion that a file once had a different name or that its reincarnation is a different file. Secure access to a repository is a pain, especially if you’re using windows. Commits are per-file instead of per-changeset. It is a pretty poor tool for code management, but it’s well known, and it works.
Now that Subversion and GNU arch are becoming more and more widely used, I’ve been checking out some of the newly available VCSes.
After reading a couple of webpages, I have decided to go with Subversion. The two important reasons for this are the fact that Subversion runs much better on Microsoft Windows (a couple of my projects are in MSVC), and that migration from CVS to Subversion is quite easy.
Other than that, arch is a nice project and I’d really like to switch to using arch once it is stabler and has improved win32 support (if it ever will..).