Simon Fell > Its just code > January 2004

The Microsoft SOAP toolkit is dead If you don't / can't go all the way to .NET, now's a good time to start looking at PocketSOAP

Cory Doctorow has a great post on Boing Boing about not getting locked into DRM, and sticking with more open formats, I totally agree, I don't understand why there are people who have spent large chunks of time ripping their CD collections to WMA (or ACC), then proceed to complain that device X doesn't support it, why would you lock yourself in like that?

Sean & Scott have an interesting question about copyrighting a WSDL doc. As they point out, its just a document so it should be copyrightable (IANAL), many of the w3c schemas are copyrighted and I don't see it being any different to that. But what does that mean for the service its describing ? the copyright on the WSDL doesn't limit your ability to use the document, only WRT to copying / distributing it. I don't see how copyrighting the WSDL can have any affect on providing a service that implements that interface without some additional contract. Perhaps that's why the Microsoft.com download info WSDL was buried in an EULA package (for example) ?

The Crystal Method were playing at the Virgin Megastore in SF for the release of their new CD, I went over to check it out, get a signed copy of the new CD, and a photo :)

Congrats to Dave & crew on shipping SOAPScope v3.0, the run as service and support for handling compressed HTTP messages are my favorite new features.

I'm trying to make sense of this statement in the docs

Only application code is impersonated; compilation and configuration are read as the process token. The result of the compilation is put in the "Temporary ASP.NET files" directory. The account that is being impersonated needs to have read/write access to this directory.

If the compilation is done with the process token, then why does the account doing the impersonation need write access to the directory ? what am I missing here ?

Welcome to the first release of 2004, v2.2 of the WSDL Wizard, it adds support for hierarchies of complex types, improved xsi:nil support and fixes some bugs to do with soap headers. Thanks to Anant and the rest of the sforce.com guys for their code contribution.

Well, you can't no more, like a lot of other people I got sick of comment spam, got something to say ? get your own blog!

Hah, the roll over worked fine :)