6 items tagged “xmlrpc”
2008
Dare left something out (and it’s important). Dave Winer: “You should at least learn the lessons and add to REST what it needs to catch up with XML-RPC. Seriously. What’s missing in REST, btw, is a standard method of serializing structs, lists and scalar types.” That would be JSON. # 18th August 2008, 9:39 am
2007
supervisor2. I haven’t tried this yet, but looks like a decent process monitoring tool. It even has an XML-RPC interface. # 8th January 2007, 1:19 am
2006
Why JSON isn’t just for JavaScript
Dave Winer’s discovery of JSON (and shock that “it’s not even XML”) has triggered an interesting discussion thread, on his blog and elsewhere. Plenty of people have re-assured him (and themselves) that it’s only used for JavaScript—it’s convenient in the browser but irrelevant elsewhere.
[... 787 words]2005
Testing a new version of IXR
Almost two years to the day since the last release, I’ve put together a new version of IXR, my PHP XML-RPC library. I haven’t published it on the site just yet as I want to make sure any bugs are ironed out first, but you can grab a copy here:
[... 177 words]2002
The Two Way Web
Dave Winer: The Two Way Web. The Two-Way-Web is a vision for the Web as an easy writing and publishing environment
. This is an old essay from March 2001 (I only found it today) which describes a vision of a web where content can be quickly and easily edited through a variety of tools, which communicate with content management systems using XML-RPC and SOAP. This is all stuff I’ve been thinking about recently, so it looks like I’m only a year and a half behind Dave ;)
Meta weblog API
I’m itching to get an XML-RPC interface to this blog up and running so I can start playing with blogging tools (or roll my own in PythonCard). It looks like Dave Winer’s MetaWeblog API is just what I need. It describes an XML-RPC interface with 3 methods: metaWeblog.newPost, metaWeblog.editPost and metaWeblog.getPost. More importantly, the standard supports complete flexibility in the data that is sent along with the request. My entries consist of a body, an optional permalink (one is generated if none is specified), optional categories and an optional search string for a “Google It!” link if one is required. The MetaWeblog API looks ideally suited to handling this, and is fully extensible should I change the format of my entries in the future.