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:
|
...can be contacted by
and followed on Twitter.
|
|
|
|
February 11, 2009 16:20
Mobile Monday London
met last night to discuss the Mobile Web and Widgets. It was an engaging and
thought-provoking evening.
Your intrepid reporter was there and, in spite of the crashing of his sad, clunky old
Windows Mobile Xperia X1, losing all his notes, he brings you this hot report from
right out of his memory (somewhat steamed up by subsequent socialising, but reclarified by
Google).
After that, I give an explanation of why I believe that Widgets are not the solution
to what Mobile 2.0 needs...
...
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
...
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
...
June 26, 2007 15:17
Web 2.0's definition
includes seeing the Web as an application platform. Which means it
is in competition with Java and .Net, and with SOA, for both local
and widely distributed applications.
If the Web is going to be a platform, the skills you need to learn
to program it are the core Web 2.0 technologies such as Ajax, JSON,
Atom, Microformats and OpenID.
And Ruby. This language, that's capturing the hearts of many Web 2.0
programmers, is ideal for easing the transition from the Java
and .Net platforms to the Web platform, as I will show.
Even if you're part of a big company that is generally immune to the
latest trends, the marriage of Ruby and the Web-as-platform may be
something to prepare for. It could even displace your SOA agenda...
...
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
...
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
...
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
...
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
...
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
...
June 15, 2006 00:30
It gives me great pleasure to announce the 2006 'What Now How'
Awards for REST Protocols (or 'APIs') in the Read/Write
Category.
All this year's awardees share the distinction of being truly
worthy of the 'REST' label; these Read/Write Protocols are
acknowledged here for their uncompromising adherence to the
simple principles of the World Wide Web.
...
May 25, 2006 19:05
The vast majority of supposedly 'REST' Web APIs are simply
abusing HTTP to carry function calls. I call
these APIs 'Service-Trampled REST', or STREST.
STREST APIs come with specific costs which could stifle
the two-way data Web (Web2.0) if allowed to propagate
unchecked. Although 'mashability' is a supposed benefit of the
current proliferation of APIs, true interoperability and
scalability can only be guaranteed by true REST interaction.
This is not an academic, purist or aesthetic stance, but one
based on practical consequences, as I will explain.
...
|
|
|
|