15 items tagged “xmlrpc”
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
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]
Harry Fuecks has been hacking on my XML-RPC library, and has released a new version with some significant changes. His article on phpPatterns describes the changes and provides a link to download the updated code. He’s made a bunch of interesting architectural changes which take advantage of a number of useful PEAR classes, including HTTP_Request which provides support for proxies and authentication, two frequently requested features.[... 127 words]
I’ve fixed a small but vital bug in the Incutio XML-RPC library. The library was causing errors when certain unicode characters were used in strings. This is because I was using PHP’s
htmlentities() function to encode strings before transmission. This escapes all of the characters that need escaping (<, >, &, " and ’) but also escapes a number of other characters that have an HTML entity equivalent. The problem is that these additional entities are defined in HTML but not in XML, so XML parsers were choking on them when they tried to parse the resulting message. I’ve fixed the bug now by switching to using
htmlspecialchars() instead. Thanks to the several people who reported this one (it took me a while to figure out) and to Marc Logemann who’s blog entry finally helped me crack it.
[... 35 words]
I’ve implemented two example web services to demonstrate the Incutio PHP XML-RPC library’s capabilities. The services allow you to search and retrieve articles from FOLDOC and the Jargon File, two popular freely available online dictionaries.[... 349 words]
Announcing beta 1.5 of IXR, the Incutio XML-PRC Library for PHP. The library has undergone a complete restructuring and has a much cleaner design as a result. It also has a huge stack of new features, including:[... 96 words]
I was up most of the night working on a new version of my XML-RPC library (newly named IXR, for Incutio XML-RPC). I should have it ready for release some time today—it implements most of the extensions I’ve linked to over the past few days and has a much cleaner object structure than the first version, while maintaining the ability to implement a server or client in as little code as possible.[... 118 words]
I spent most of yesterday messing around with XML-RPC. There are a variety of XMl-RPC libraries available for PHP but none of them felt right for what I needed. So, I’ve written my own.[... 115 words]
Via techno weenie: A Python XML-RPC debugging proxy script. This solves the problem of XML-RPC errors from PHP being sent out with the XML-RPC response packet and breaking any XML parser trying to recieve the packet. Instead you can test your script by aiming at the proxy script which will dump any problems to the console for you.[... 70 words]
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 ;)
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.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.