Excellent!! New posts in RU get XML_RPCed to my test Conversant weblog at http://www.smeed.org/cruxial/

The first two attempts were winged on their way up to Dave's test ManilaBlogger site. [Haven't (yet) had the courage to go and check to see if they turned up there! ;-)]

Although susbsequent attempts hadn't appeared to work they in fact had been 'held for delivery' and once I sorted out the correct script path, the try clause in conversantBridgeSuite.publishItemCallback() succeeded and off they went - arriving asynchronously so they aren't necessarily in the correct order ;-)

How neat is that! This framework is pretty damn cool! It even copes with hacked scripts that I break ;-)

A big thankyou to Dave and Greg for making this all possible. Now that I have newPost() working, I'll crack on with editPost() and deletePost() taking into account the fact that Conversant ids are not the same as blogger ids.

A comparison of Conversant's XML-RPC Interfaces[166 methods] with the Blogger API [6 methods] is pretty revealing.

What this means is that it's going to be relatively trivial to support the equivalent of Blogger's 6 methods, but controlling even a fraction of the functionality of Conversant with Radio is just not a viable option. So, I'll just be using Radio to route posts to my Conversant site and, perhaps, editing them offline. I doubt very much I will be using Radio to participate in my discussion forums or to use it to adminsister my Conversant sites.

Nevertheless, Radio is going to be a great tool for collating RSS feeds, etc., and publishing the links. A job which it does extremely well.

Onward...