Tag Archives: architecture

Users and self-description

I’ve had a couple of conversations recently – one online and one off – that both centered around an important aspect of distributed computing that is often overlooked: the role of users in determining message semantics. When we write and deploy software, either client or server, it is easily forgotten that this software has been… Read More »

Only the best, detest

While reading the comments in Steve’s initial ESB post, I spotted a paragraph that nailed the elephant-in-the-room meta issue on the head; Its funny but so few people who also use ESB and WS-* style protocols and tools frequently operate with such disdain for other ways of doing things. There are, of course, a very… Read More »

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 »

REST the hard way

Stu Charlton responds to my comment (and Mark’s) about how Pat Helland did things the hard way in discovering REST in a recent paper of his; So, while the two Marks are suggesting Pat’s reached REST the hard way, I would suggest this is something he’s been saying for years, […] That is the hard… Read More »

What’s Next for Browsers?

Paul writes that innovation in the browser ain’t dead yet. I agree. From a distributed systems POV, I think there’s two important things that need to happen to the browser, in addition to the richer languages that Paul talks about (and don’t forget about RDF and OWL!); making the browser a peer allowing the browser… Read More »