Posts tagged 'dialogue' | What Not How | http://duncan-cragg.org/blog/

About All Things...

Declarative, Mobile 2.0, REST, Cloud, Web 2.0, Ajax, Publish / Subscribe, Event-Driven Architectures, JSON, Atom, Microformats, Linked Data, P2P, Identity, Copyright, Multimedia, Cyberspace.

...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 'dialogue'


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... ... Read "FOREST: a GET-only REST Integration Pattern" architecture ■ ■ app ■ ■ dialogue ■ ■ rest ■ ■ rest-observer ■ ■ forest ■ ■ 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 ... Read "Web Objects Ask, They Never Tell \| The REST Dialogues" semanticweb ■ ■ architecture ■ ■ declarative ■ ■ publishsubscribe ■ ■ p2p ■ ■ app ■ ■ microformats ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ scalability ■ ■ rest-observer ■ ■ WS-Are-You-Sure \| The REST Dialogues July 16, 2009 16:16 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 8: WS-Are-You-Sure (Security, Reliable Messaging and Transactions) ... Read "WS-Are-You-Sure \| The REST Dialogues" architecture ■ ■ declarative ■ ■ publishsubscribe ■ ■ p2p ■ ■ app ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ atom ■ ■ Business Conversations \| The REST Dialogues December 11, 2008 11:45 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 7: Business Conversations ... Read "Business Conversations \| The REST Dialogues" architecture ■ ■ declarative ■ ■ strest ■ ■ app ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ Content-Types and URIs \| The REST Dialogues February 16, 2008 23:44 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 (GetSearchResults, GetItem, GetCategoryListings, etc). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 6: Content-Types and URIs ... Read "Content-Types and URIs \| The REST Dialogues" architecture ■ ■ declarative ■ ■ strest ■ ■ microformats ■ ■ dialogue ■ ■ rest ■ ■ atom ■ ■ The Distributed Observer Pattern \| The REST Dialogues June 20, 2007 22:42 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 (GetSearchResults, GetItem, GetCategoryListings, etc). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 5: The Distributed Observer Pattern ... Read "The Distributed Observer Pattern \| The REST Dialogues" architecture ■ ■ declarative ■ ■ strest ■ ■ publishsubscribe ■ ■ app ■ ■ microformats ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ atom ■ ■ Inter-Enterprise REST Integration \| The REST Dialogues April 8, 2007 13:38 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 (GetSearchResults, GetItem, GetCategoryListings, etc). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 4: Inter-Enterprise REST Integration ... Read "Inter-Enterprise REST Integration \| The REST Dialogues" architecture ■ ■ declarative ■ ■ strest ■ ■ p2p ■ ■ app ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ atom ■ ■ scalability ■ ■ Business Functions \| The REST Dialogues January 10, 2007 14:21 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 (GetSearchResults, GetItem, GetCategoryListings, etc). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 3: Business Functions ... Read "Business Functions \| The REST Dialogues" architecture ■ ■ declarative ■ ■ strest ■ ■ app ■ ■ dialogue ■ ■ event-driven ■ ■ rest ■ ■ atom ■ ■ scalability ■ ■ Setting Data \| The REST Dialogues November 15, 2006 23:37 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 one of the many function calls that they make available via SOAP (GetSearchResults). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 2: Setting Data ... Read "Setting Data \| The REST Dialogues" architecture ■ ■ declarative ■ ■ web2.0 ■ ■ strest ■ ■ app ■ ■ microformats ■ ■ dialogue ■ ■ rest ■ ■ atom ■ ■ Getting Data \| The REST Dialogues November 14, 2006 00:05 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 one of the many function calls that they make available via SOAP (GetSearchResults). In this dialogue series, I argue the case for eBay to adopt a truly REST approach to their integration API. Part 1: Getting Data ... Read "Getting Data \| The REST Dialogues" architecture ■ ■ declarative ■ ■ web2.0 ■ ■ strest ■ ■ app ■ ■ microformats ■ ■ dialogue ■ ■ rest ■ ■ atom ■ ■