Open Standards and Smart Developers
I've been playing around with some of the more non-standard XML-RPC editors like "Zempt" in an effort to get a better understanding of what the entire continuum of offerings looks like.
I say "non-standard" because there is an emerging category of editors that not-only support the base standard, but also only those specific extensions that specific blog applications might make to the base standard. MovableType, for instance, is probably the most supported "extended interface". MT does things that go well above and beyond the basic implementations that others have settled on. For instance, I don't believe that returning a list of text fiters during logon is part of "the standard" - but when Zempt is used in conjunction with MT, Zempt specifically queries the server for an indication of what text filters are installed and the MT server dutifully responds with a list.
Zempt, therefore, probably shouldn't work with other blogs that don't support the Movabletype extensions.
But it does work with blogware. :) In fact, that's what I'm using to write this particular post.
Zempt is smart enough not to fatal error when it doesn't get a list of text filters back from the server and Rblog is smart enough to support enough of what MT does to be Zempt compatible. I'm not sure whether or not this is true of other blog applications, but I am pleased that ours does. Personal pride in our guys forethought I suppose.
If you've read this far, here's a treat:
If you want to post via xml-rpc, these settings work:
username = what you use to login to blogware
pasword = what you use to login to blogware
host = http://www.blogware.com
RPC endpoint/page/target = /xmlrpc.cgi
Let me know if this doesn't work for you, or if you need further clarifications on how to use it with specific clients.
See this post as it first appeared on Blogware.