OK - so, the summary API/Ajax thoughts... APIs - are good. We love APIs. - They give as much benefit within an organisation - (linking up internal systems) as they do when publically exposed (mashups) - There are different flavours of API, and the right API should be used for the job; always use the appropriate technology, (whilst ensuring you can migrate to a newer more appropriate technology further down the line??) - APIs are the foundations of the shift to a 'service layer based world' (anyone want to expand on that concept? It's a nice one...)
AJAX - Is currently the best way to build responsive, in-browser application like experiences for performing actions on data* - AJAX is more than just a scripting language; it too can be the 'appropriate technology' for an API - AJAX should be used when a site needs a responsive interface whilst being mindful of graceful experience decay - It's not magic web pixie dust - you need to design your interface for your intended audience. Our current design patterns serve a niche. - Is - generally speaking - operating at a layer above the API, providing the tools for the user to manipulate the data the API offers up (this one will get me shouted at, I think?) HTML - At the root of everything, standards compliant, with presentation separate from content. *I'm thinking, something along the lines of Ajax for what ajax does well... Namely thing X, and flash for what flash does well, namely thing Y. For values of Y approaching 'nice animation, games, interactive entertainment', and X approaching 'operations on XML, dynamic sites and databasey stuff...' But I kind of hit my technical limit in describing X. Anyone? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luke Dicken Sent: 17 July 2006 10:57 To: backstage@lists.bbc.co.uk Subject: Re: [backstage] Web2.0 - tennets, rules, development philosophy... I'd love you to give us some feedback Daniel Morris wrote: > Firstly, the list seems fairly comprehensive and easy to read. > Secondly, apologies if there are obvious answers to this email, i'm new... > > How come REST API gets mentioned, but ajax doesn't? > > I know ajax is an overused buzzword at the moment, but it is > unavoidably crucial to the web2.0 push. > Specifically in closing the gap with desktop applications in terms of > application richness / responsiveness. > > Also, although APIs and services are mentioned, perhaps this could be > accented more? > The move to a service-layer based world can be a substancial paradigm > shift. > > -dan > AJAX is a language/technology not an API - HTML doesn't get mentioned either, its still a safe bet that it will be of relevance to web2.0. - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/ - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
