Duncan Cragg on Declarative Architectures
About All Things...
...taking programming beyond:
Threads, Message Queues, Client-Server, CORBA, Web Services, SOAs, Agents, Synchronous Architectures, Imperative Programming - and even Applications, Desktops and Documents
Duncan Cragg...
...works for ThoughtWorks UK; originally from April 2002 to July 2007 and now recently re-joined. Previously worked as a Web Architect for the Financial Times.
...went to both UCL and Imperial College of the University of London (in the Eighties); specialising in Logic during his MSc.
...wonders when his LinkedIn Account will be useful
...has a phone-cam, and used it on himself once, just before his weekly shave:
Photo of Duncan Cragg
...can be contacted by and followed on Twitter.
Posts tagged 'rest-observer' Atom Feed for Posts tagged 'rest-observer'
March 18, 2010 16:58

Around the middle of February I completed a basic persistence and networking implementation for Fjord, then had to do other things for a month. Just recently I fixed Fjord to work with the latest version of the Node.js APIs.

Next project: I'm going to use Fjord in a Web Framework to be called "JSON-Mash".

I intend to show that JSON-Mash will be a great framework for rapidly building truly interoperable and truly scalable online and distributed functionality.

Here's how JSON-Mash will work.   ...

FOREST: a GET-only REST Integration Pattern
October 9, 2009 17:14
Updated: October 11, 2009 11:46

Since the day in 2006 that our dialogue took place with an imaginary eBay Architect, he has been promoted to imaginary Enterprise Architect in an investment bank! Convinced by the merits of REST, he took his enthusiasm for it into his new job and embarked on architecting a trading system using REST or ROA as an alternative to SOA.

Now, he hit upon a snag: he had a REST "bank server" generating bids on an instrument and POSTing them into that instrument's REST "market server". But then he had two copies of his bid! One held by the bank server on one URI, and the other in a "bid collection" held by the market server's instrument - on another URI.

He asked himself: "Which URI is the real one? Which host 'owns' the bid? Is the market's copy just a cache? If so, why does it have a new URI? Why doesn't the market host know the URI of the bank's original bid? Why can't servers become clients and just GET the data that their own data depends upon?" The server seemed to be dominating the conversation, not letting its 'client' server have a say in things.

Our worried Enterprise Architect noticed that such Service-Orientation permeated REST practice: there were "REST APIs" to Web sites, or "Web services" with a small 's'. Even AtomPub had a "service document"! Some patterns, like AtomPub, offered just simple read/write data services through the full HTTP method set. Some simply used such a read/write interface as a wrapper around more complex service functions.

He wondered: "Where's the Web in REST integration? The Web works great without PUT and DELETE: isn't using GET on its own RESTful enough?"

So, remembering something I said about "Symmetric REST", he contacted me again...   ...

FOREST: Functional Observer REST
October 6, 2009 10:28

  • Functional Observer REST = Hyperdata Interdependency requiring Symmetric REST
  • Hyperdata Interdependency = a resource's state is a Function of its linked resource context
  • Symmetric REST = servers become clients in order to Observe the dependencies of their resources


Web Objects Ask, They Never Tell | The REST Dialogues
August 13, 2009 11:43

In an exclusive nine-part dialogue with an imaginary eBay Architect, we present an accessible discussion of the REST vs. SOA issue.

Although eBay have what they call a 'REST' interface, it is, in fact, a STREST interface, and only works for a few of the many function calls that they make available via SOAP.

In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API.

Part 9: Web Objects Ask, They Never Tell   ...

Recent Posts
EUP, IoT, AR and Minecraft | NetMash | Object Network
CoAP and a Web of Things watching Things
The Object Network Approach to Augmented Reality and the Internet of Things
Building The Object Network
Cyrus in 2013
Empowering the World | NetMash
Fun and Virtual Worlds | NetMash
The Basics | The Object Network
Why we should link up our Web APIs | The Object Network
Introduction | The Object Network
OTS: The Benefits of both Native and Web Mobile
Mature REST In Six Lines!
Minted Media Types are Usually Less RESTful Than JSON