I just skimmed through "From XML-RPC to SOAP, A Migration Guide", and I can't help but thinking this is the wrong approach. First off, a SOAP client can't actually use an existing (unmodified) XML-RPC implementation. This migration guide calls for changes to the old implementation -- although I guess slow movement what migration is all about. Second, it just seems like it would be easier to provide a converter that would rewrite SOAP requests so the XML-RPC server could process them:

• strip off the envelope and body tags
• sanitize any namespaces
• munge the headers if necessary

This way, the client doesn't have to be "backwards compatible", and the server doesn't have to be retrofitted. I guess I should provide an implementation, but I'll leave that as an exercise for the reader...

This is pretty simple. All I did was to convert the MS KB article from Visual Basic to Python. Note that this won't actually create the .mdb file. That's a little trickier -- I can't find a Python binding for the DLL call and I don't have the need for it at the moment. See init_dsn.py for details.

If you are a charity, and you interrupt and harass me on the phone, don't wait by the mailbox for anything from me.

That goes double if you're not a charity and you're trying to make money by calling and harassing me on the phone. I'm at least polite to (what I presume, perhaps wrongly, to be) the volunteer telemarketers.

By the way, I'm considering a name change from "not quite random" to "mean old bastard". I wonder if it's already in use?