Simon Fell > Its just code
Friday, March 15, 2002
Wot no CoCreateGuid ? WinCE doesn't support the CoCreateGuid API (unless you have the DCOM bits, which no one ships), so I've been writing my own version, this relies on the IPHelper API to get the MAC address of the network card (if there is one). The docs claim that this is supported on PocketPC 2000, but the PPC2000 dev environment is missing it, I've built a version with the PPC2002 dev environment, I'd be interested to know what happens when you run it on PPC2000. There's an ARM build available at http://www.pocketsoap.com/pocketsoap/attTester.zip If someone would like to give it a go.
Someone should give the WinCE API doc writers a copy of eVC. The docs for srand have a nice little sample that uses time from time.h, pitty eVC doesn't ship with a time.h !
Dare Obasanjo just posted on the xml-dev list that MSXML 4.0 SP1 is now available. [/serdar/] Cool, although I couldn't find a fix list, guess I'll just have to download it and try it, to see if they've fixed the SOM problem i found.
The joys of PocketPC development Despite the fact that the docs for CreateFile clearly state that you can use FILE_FLAG_SEQUENTIAL_SCAN, don't beleive a word of it, any attempt to use this results in an "incorrect parameter" error at runtime. Just don't ask how long it took me to track that down. (or how many times eVC crashed in the process)
Working on getting the PocketSOAP 1.3 beta up and running on PocketPC, finally got eVC to build everything cleanly, but for some reason eVB doesn't seem very happy since I upgraded to PocketPC 2002, it flatly refuses to download or debug to my iPaq this is somewhat hampering my attempts to test it :(
Julain Bond has a comment about the Interop Stack presented at the recent WSDL interop meeting. This is something I've been thinking about since seeing that powerpoint slide.
The further up the stack you go, the smaller the number of people will be involved (not everyone supporting SOAP is going to want to also support XLANG for example). I think what will shake out, is that groups will break out to cover the different areas (for example, a number of people have already done work on interop testing for WS-Routing and Soap with Attachments). A key move has to be to parallelize these activities, and to continue the post meeting testing, It might just be me, but there seems to be much less post meeting activity from Round 3, than there was for the earlier testing.
Coping with Change [Sam Ruby's Radio Weblog] More good stuff from Sam, he also points to this post about extensibility. This is why I prefer SOAP over XML-PRC and RSS 1.0 over RSS 0.92, because they are extensible in a non-centralized manner (using namespaces). For example, a while back I wanted to syndicate information about time based events, RSS 1.0 allowed me to compose in the additional metadata I wanted (and in fact, I was able to re-use some standard metadata defined by Dublin Core), whilst RSS 0.92 required me try and get the spec rev'd, and whilst there is now a RSS 0.93 spec, its appears to be pretty much dead in the water.