Tag Archives: webarch

REST as a long bet?

I have to say, I’m with James in his response to Sam’s long bets; To say, as Sam and Tim both do, that REST is important is like saying the fan in my laptop is “important”. There’s really nothing to discuss about it. RESTful services are fundamentally critical to the continued evolution of the Web.… Read More »

How not to bridge XMPP and HTTP

BOSH is a specification that defines how XMPP can be used over HTTP. It’s obviously written by people who know what they’re talking about, because they’ve got good requirements, and get into great detail about the design choices they’ve made. Unfortunately, BOSH makes the one big mistake that so many others make; treating HTTP as… Read More »

Nouns, verbs, oh my!

It’s nice to see Pat Helland join the REST/SOA conversation. His first post is in a rather quisical, loose style that I hadn’t seen before, but that’s ok, I think I get what he’s talking about. The point seems to be summed up here; Is the purchase-order (or even the line-item) a noun or a… Read More »

REST, WADL, forest, trees

I’m kinda busy with a bunch of things on my plate, but felt I had to chime in on the latest calls for a RESTful description language ala WADL. Aristotle’s response struck a chord; […] there isn’t much to describe; there aren’t any methods or signatures thereof to document, since access to resources is uniform… Read More »

New voices

I’m absolutely thrilled that Tim has finally grokked REST. AFAIK, he’s the first die-hard Web services type with a strong public persona to realize REST’s (and the Web’s, of course) benefits over WS/SOA/RPC. Bravo, Tim! I’ve long thought that what was needed in this discussion was new perspectives on the relationship between REST and WS/RPC/etc…… Read More »

GET/POST described

Don’s latest on GET is interesting (especially “That’s certainly where I’m investing”!), but I really liked this bit of Tim Ewald‘s comment; The solution is a minimal footprint interaction, like a coarse-grained document transfer via a pin-hole, a la’ a Biztalk port. Exposing all your data via GET so anyone can read anything they want… Read More »

More on human targetting

It sounds like Sanjiva’s as baffled as I am how we can each hold the positions we do about what seems like a completely trivial point. He responds to my previous piece on the Web being for humans, and writes; The problem with GET is exactly what Mark points to as its feature: GET is… Read More »