Posts tagged 'p2p' | 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 'p2p'


CoAP and a Web of Things watching Things May 19, 2014 21:21 With the expansion of the Internet of Things (IoT), and the diversity of products and technologies, the one thing that everyone agrees on is that it's time to start agreeing: the Internet of Things needs standards. Many agree that it needs open standards, like those that underpin the Web. Obviously, a Web of Things is going to be quite different from the Web of Documents and Applications: it'll be much more fine-grained and much more "buzzy", with many sensors and actuators working together with many hubs and services. It's more likely to be at home with the next generation of the Internet Protocol: IPv6. To meet the fine-grained and buzzy nature of the IoT, the Constrained Application Protocol, or CoAP, was created. CoAP is an open Internet standard for the Web of Things. It's based on the Web's core pipe: HTTP, but has many differences to allow it to be used by very resource-constrained devices and local radio networks. CoAP can be used in many different ways, but there's a danger that a lack of clarity in exactly how it's used means it doesn't achieve its full potential to link up the world's embedded devices. This article proposes a simple and clear way that CoAP could be used to build a uniform, global, decentralised Web of interacting and discoverable Things. This article first appeared on the ThoughtWorks Insights pages. ... Read "CoAP and a Web of Things watching Things" architecture ■ ■ p2p ■ ■ forest ■ ■ cyrus ■ ■ object-network ■ ■ IoT ■ ■ The Object Network Approach to Augmented Reality and the Internet of Things March 1, 2014 11:24 After filling up that other blog recently with 61 pages of content, one page a day, I was challenged by my ThoughtWorks colleague, Andy McWilliams, to help him get in more easily to my explanations of the Object Network applied to Augmented Reality and the Internet of Things, especially around how my approach differs and is better than other approaches. ... Read "The Object Network Approach to Augmented Reality and the Internet of Things" architecture ■ ■ declarative ■ ■ p2p ■ ■ rest ■ ■ json ■ ■ forest ■ ■ netmash ■ ■ cyrus ■ ■ object-network ■ ■ IoT ■ ■ 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 ■ ■ The Mobile 2.0 Killer App is the App Killer December 19, 2008 17:05 Mobiles are unique - if you want to miss out on the opportunity they represent, you could choose to see them as just slow computers with tiny interfaces and dodgy Internet connections. Then try to squeeze in your traditional applications; try squeezing the office desktop metaphor with its sedentary documents into a device the size of a mouse! Alternatively, see them as the most personal, social and dynamic of devices that are becoming connected to the Internet. Now a multi-billion-scale global opportunity opens up to you. That's customers and dollars! In trying to grasp this, some are calling it 'Mobile 2.0', by analogy with its sibling, Web 2.0. In that light, the Killer App for Mobile 2.0 is the sharer, masher and updater of People, Things, Times and Places... The key to getting Mobile 2.0 right is for it to merge seamlessly into our lives. That means the handling of dynamic and shared data becomes the top priority, even above the handling of applications. This article describes a Mobile 2.0 platform that makes people and their stuff first class - not applications. ... Read "The Mobile 2.0 Killer App is the App Killer" architecture ■ ■ declarative ■ ■ web2.0 ■ ■ yaml ■ ■ socialsoftware ■ ■ identity ■ ■ publishsubscribe ■ ■ p2p ■ ■ multimedia ■ ■ event-driven ■ ■ mobile2.0 ■ ■ The Universe Web July 18, 2008 19:49 Since the announcement by IBM and Linden Lab that OpenSim can talk to Second Life, I've been thinking again about RESTful Virtual Reality. I'm not the first, of course. Others have been motivated by the same goal: To bring the Web's scalability, linkability and interoperability into Virtual World platforms. Ultimately, how to use the same techniques as the Web to link Virtual Worlds together into a single, massive 'Virtual Universe'. Here's how I would architect the Universe Web... ... Read "The Universe Web" cyberspace ■ ■ architecture ■ ■ declarative ■ ■ socialsoftware ■ ■ publishsubscribe ■ ■ p2p ■ ■ rest ■ ■ scalability ■ ■ json ■ ■ metaverse ■ ■ Google Micro Conference October 5, 2007 11:22 Last night's Google London Open Source Jam (also here) was on the subject of the 'Web' (didn't they invent that? Oh no, that was Microsoft). This event has been getting better and better each time I've attended. There were some very interesting lightning talks held together with a tight structure and plenty of chance to chat, drink cold Leffe and eat cold pizza. And nick [transatlantic translation: 'steal'] the Green & Black's chocolate. An ideal Micro Conference... ... Read "Google Micro Conference" web2.0 ■ ■ atom ■ ■ ajax ■ ■ rest ■ ■ event-driven ■ ■ publishsubscribe ■ ■ p2p ■ ■ architecture ■ ■ declarative ■ ■ app ■ ■ microformats ■ ■ scalability ■ ■ json ■ ■ openid ■ ■ microweb ■ ■ google ■ ■ 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 ■ ■ The "Imperative to Declarative Inversion": Open Data is OK! May 11, 2006 21:36 There is something about the Internet that nurtures open data, and something about computers that nurtures closed. It is often necessary, but often painful, to make the jump from local, closed data to global, open data. ... Read "The "Imperative to Declarative Inversion": Open Data is OK!" copyright ■ ■ architecture ■ ■ declarative ■ ■ publishsubscribe ■ ■ p2p ■ ■ rest ■ ■ Welcome to 'What Not How' March 22, 2006 17:00 Declarative Architectures focus on the What, not the How, of programming. The How has dominated the field - perhaps 80% of programming is done in the traditional Imperative style, where we tell the computer How to do a task in explicit steps. I'd like to show in this blog how Declarative Architectures and technologies are not just an interesting sideshow to the main Imperative attraction, but a complete and powerful programming alternative in their own right - indeed, one which has already dominated certain fields. Imagine being able to simply express What we want the computer to do - to give it constraints and rules - then let it work out for itself How to achieve our goals. I believe that saying What, not How, will become the dominant paradigm in programming. ... Read "Welcome to 'What Not How'" semanticweb ■ ■ architecture ■ ■ declarative ■ ■ web2.0 ■ ■ socialsoftware ■ ■ p2p ■ ■ event-driven ■ ■ rest ■ ■