Scottish lass seeks...

Scottish net feminist seeking digital enlightenment, geek fulfilment, promotion of Scottish women on the world map and, oh aye, global harmony. The quest to re-engineer Quine Online. (www.quine.org.uk)

Updated: 19/10/2002; 01:11:15.

05 April 2002

Queen Mother's Funeral procession

"The Queen Mother's coffin will be carried in ceremonial procession on Friday morning to the Palace of Westminster where it will lie in state until Monday." [BBC]
The BBC will be providing Live webcasting of  the Queen Mother's Funeral 2:00:34 AM    

DaveNet: Four Years of XML-RPC.
"...XML-RPC evolved to become SOAP, which is more famous -- if you pay attention to the press and analysts and the execs at BigCo's. But if you listen to developers, they're choosing XML-RPC in droves, because of its simplicity, broad support, and lack of confusion about what it is and where it ends..."  [Scripting News]

Amen. I've just been spending the last 4 nights bashing my head trying to get the CGI version of a Perl SOAP server working using SOAP::Lite, I can get the command-line version going no problem but there's some screw up in communication between Radio client and the Perl server that is causing problems. It'll turn out to be me not intialising something to the right value through lack of understanding I'm sure. Trying to debug this is very time consuming. Under XML-RPC I was able to make it work first time both with Perl and PHP. The very complexity of SOAP is what makes the heart of a developer grow weary. I'm sure persevering with SOAP will be worth it and all the extra bells and whistles will solve business problems, but for a developer just interested in gluing useful code together quickly and simply, XML-RPC rocks - especially for the kind of apps where all you want is simply to trigger running some complex server-side code from a remote client. You are spoilt for choice when it comes to implementations. Do we really want to spend more time coding the 'glue' than the actual apps themselves...I don't think so. Talking of complexity, take a look at JavaTM Web Services Developer Pack (JavaTM WSDP) Sophisticated yes,  but just how many damned acronyms do we need to know and what bare minimum APIs are necessary to get up and running? Their HelloWorld example needs no less than 5 files. Haud me back.

 1:45:59 AM    

© Copyright 2002, Scottish Lass, www.scottishlass.co.uk, Contact: Click here to send an email to the editor of this weblog..