Monthly Archives: January 2003

HTTP Guru for Hire

Scott Lawrence joins the ranks of HTTP gurus looking for work. If you need somebody who understands HTTP (not sure if he groks REST though), you couldn’t do much better than Scott.

WSDL Support for Application Protocols

I just sent this message (with this followup) to the Web Services Description WG to try and get first class support for application protocols (rather than requiring that they be treated as transport protocols) into WSDL. Let’s see how that goes.

Irregular Verbs Hurt

Sean McGrath with another fine article about REST. I had also been using the grammatical metaphor recently in some off-line discussions, to try and explain visibility. The one interesting nugget that emerged from that exercise, was that application protocol headers are adverbs, as they modify the verb (method). So a GET with an If-Modified-Since header,… Read More »

APIs and Application Protocols

Like many other discussions (though perhaps much faster than most 8-), Simon gets to the heart of the matter; […] but at that level so is SOAP, its always HTTP POSTs[…] While trying not to sound too much like a broken record, there is just one “level” here, the application layer; HTTP methods are application… Read More »

Composing Web Services; Choreography vs. Routing

Simon Fell says that he has trouble understanding some of my arguments, in particular this one where I attempt to outline the value of pipe-and-filter style composition over a choreographed solution. Let me elaborate here then. It’s long been recognized that composition of components is simpler and more tractable when those components share an interface,… Read More »

So Where Does the Method Go?

James Strachan asks that if the method doesn’t go in the SOAP envelope, could it go in the URI or an HTTP header? My answer would be “No”, that in order to gain the benefits of REST, the only method you need should be the one in the HTTP request line, such as GET/PUT/POST. That’s… Read More »

W3C Choreography Working Group Chartered

More tail-chasing going on over at the W3C with the chartering of the Web Services Choreography WG. I’m really disappointed that Tim didn’t take this opportunity to speak his mind about the mistakes being made with Web services, especially considering that this working group exists to replace the hypermedia application model, which is pretty darned… Read More »

What does a Trackback URI identify?

Sam Ruby implements the RSS Trackback module in his RSS 2.0 feed. It’s implemented by simply including a “trackback:ping” qualified URI in the item. For the item that corresponded to his announcement of support, the URI is; http://www.intertwingly.net/blog/1105.tb So being the Web-head that I am, I invoked GET on it. Here’s what I saw; <?xml… Read More »

Reusing HTTP where you wouldn’t expect to see it

A nice surprise turned up in my IETF mailbox this yesterday, Applying WebDAV to Network Configuration Management Problems. This memo examines the potential of using WWW Distributed Authoring and Versioning (WebDAV) technologies to address the problems of network configuration management. It reviews requirements and issues that have been identified in IETF network configuration management and… Read More »

Dead Airport

I awoke this morning to a dead Wifi network in my house. Oh joy. Close to three years of pure bliss of 802.11b in the whole house, then nothing. A quick investigation turned up an almost identical report explaining the state of my base station. It looks like it’s totally dead. In the mean time,… Read More »