Opening The Web

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

more share options
Embed For WordPress.com

Without related presentations

Notes on slide 1

Hello, thanks for coming to my talk...

I’m a developer, 14 year old, not quite as impressive!

BinaryCake

In the beginning... take you back

1996 - Web of documents Essentially what the web is Documents describing information - Hypertext HTML + HTTP

Describe documents, describe information Structure - Headers, Paragraphs, Divisions etc

1999 - Web of media Starting to see more things Documents containing MORE Improvements in technology Media

Music new distribution platform

Photos Music Videos

2004 - Web of interaction Social Dynamic, User generated content Sharing and spreading information

Wikipedia, YouTube, Social Networks, Twitter, Flickr

2008 - Web of openness Sharing more and more Copyright Restrictions

Open source, Pirating, Feeling togetherness

Free free free! Spotify = awesome

Point of my talk -APIsMaking information easy to use, remix and redistribute

The web is huge

Expanse of information and data, anything and everything Open the web up, let content be shared

People with the content Outreach - our content is out there New and exciting ways of accessing it The service is used more frequently, by new and different people your content is going places

People getting the content Your workload is lessened Different content from different places Mash things up - putting photos on maps and maps to people

Stands for Application Programming Interface Way of adding functionality to an application

Twitter 70% of usage is from API! Other way of accessing service - widespread, global service

Giving away data and letting people use it

Giving it away in a raw format Raw data previously page crawling, nasty get what you want

How do I? Simple + Complex Return data on a query Do actions

RSS/Feeds RSS is Really Simple! updating list of a resource posts, articles, whatever easy to parse, use and obtain Still an API - giving data in a raw format Very common most blogs have built in support easy to add

REST Representational State Transfer Resources HTTP Verbs GET is GETTING data POST is CREATING data PUT is UPDATING data DELETE is DELETING data URLs Rails support ID Allows you to do more than RSS, updating and modify data easy to do programatically - it’s just calling the server, just like a web browser

XML-RPC XML Remote Procedure Calling Server defines function, you call it Uses XML for request + response Do any action - up to server to define, using XML

YQL Yahoo Developer Network SQL syntax to query for querying the net Standard Yahoo Stuff

Twitter A

Twitter B

Security Exposing functionality Authenticate!

API Keys - Shared Secret Session based login method, get a key use key easy way of authentication

oAuth Redirects to site, authenticates and leaves Make requests!

HTTP SAML HTTP Basic HTTP Encryption

Your own Facebook Connect, Google APIs all do it In fact, use them! OpenID

SSL General Rule of Thumb - if if your API does not use SSL it potentially exposes everything that your API does

Might not want to! Other routes of giving developers access then APIs Really secure systems, payment etc. PayPal Redirection etc. Right tool for the right job :)

Embedded applications Facebook Platform Apps on your site, YOUR server Generally, you don’t want to do this Security issues Build an entire platform expose any needed resources safely expose app data safely

APIs are great Share your data extra interaction from users make your site more accessible

MAKE it accessible! DOCUMENTATION, BITCH Standardised - global consistancy Think - would I understand and use this?

Cheers!yst

Favorites, Groups & Events

Opening The Web - Presentation Transcript

Opening the Web
- Jamie Rumbelow
- Tomorrow’s Web
8th August, 2009 London Photo: Flickr (jamelah)
Me! @jamierumbelow Jamie Rumbelow http://jamierumbelow.net
- AWESOME Web Dev Screencasts
- PHP, JavaScript, iPhone etc.
- High-quality + Cheap!
- http://binarycake.com
What was the web? Why should it be open? What’s an API? How can I get one? And if something goes wrong? Awesome! Awesome! Awesome! Awesome! Awesome! Awesome!
In the Beginning...
Documents Photo: Flickr (corgettelawn)
HTML - Document Structure Photo: Flickr (ninavizz)
Media Photo: Flickr (john_a_ward)
Music Photo: Flickr (lynchaos)
Interaction Photo: Flickr (wlodi)
Web 2.0 Photo: Flickr (c__)
Openness
Open Source
Free, Free, Free
APIs Photo: Flickr (foreverdigital)
Why open?
Photo: Flickr (cncphotos)
Photo: Flickr (mackz) Open Expanse of Data
What’s good about open? Photo: Flickr (devillibrarian)
Photo: Flickr (jurvetson) Your content is going places
Photo: Flickr (Radioher) Relax, it’s done for you
Err... API?
Photo: Flickr (Mikecpeck) Taking lots of data and doing stuff
Twitter
Giving your data away Photo: Flickr (Patrick Haney)
Raw Data
The Techy Bit
RSS - Frequently updating info feeds
REpresentational State Transfer (REST) Photo: Flickr (nadya) HTTP-based actions
XML-RPC Photo: Flickr (willpate)
YQL Photo: Flickr (nokiapixel)
YQL = The Hot Shiz
SELECT * FROM xml WHERE url=' http://twitter.com/statuses/user_timeline.xml?id=jamierumbelow'
SELECT * FROM twitter.user.timeline WHERE id=' jamierumbelow'
Woah, Problemo
Security Photo: Flickr (lwr)
Session-based Authentication Photo: Flickr (fallsroad)
Photo: Flickr (factoryjoe)
Photo: Flickr (alan-dean) HTTP-based Authentication
Photo: Flickr (mburpee) Custom
SSL
Lack of SSL Pain Not good!
What if I don’t want to? Photo: Flickr (slushpup)
Embedded Application Platforms Photo: Flickr (Barnaby)
Cool!
What was the web? Why should it be open? What’s an API? How can I get one? And if something goes wrong? Awesome! Awesome! Awesome! Awesome! Awesome! Awesome!
API = AWESOME (like the T-shirt) Photo: Flickr (codepo8)
Don’t hurt my soul...
Kthxbye Jamie Rumbelow @jamierumbelow http://jamierumbelow.net http://binarycake.com ‘ i metjamie’ - 10 credit s