Mashup presentation slides and links
We had a lively and inspiring session at the IT University Thursday. Here are some of the links and book titles i promised to pass on to you.
Links
- Programmableweb.com has thousands of mashups as well as a long list of available APIs for your mashup pleasure – another list here
- Google’s app platform, App Engine could be very suitable for mashups. I haven’t gotten around to trying it yet
- Yahoo Pipes is an interesting early step into the non-code heaven in the near future. You simply connect feeds with feeds using a direct interface
- Google Maps is particularly easy to mash up
Getting started, the reading way
I highly recommend these tutorials in this order
If you prefer books, take a look at the not-so-boring Head First series written keep your brain active as you learn(!) (PHP and MySQL, HTML and CSS.
The viewing way (or monkey see, monkey do)
If you’re the TV kind of person, make sure you check out Lynda.com. Here’s a PHP and MySQL video tutorial. It’s not free, but once you’ve paid the monthly fee of 25 dollars (three pizzas), you get access to more than 500 tutorials including Flash, Photoshop, and the list goes on.
Slides and cards
Planning and designing a mashup
View more presentations from mortenjust.
March 30th, 2009 at 3:50 pm
Great list…
I’ll only add that Google App Engine is perfect for many kinds of mashup — but certainly not all. There are a few caveats:
- It’s (almost) python-only. That’s cool if you love python but would scare aware people just coming to php programming.
- Your access to disk, data storage and the wide web is limited. Take for example python-twitter (obviously, a popular api implementation of twitter in python). It’s caching scheme is based on disk access and thus won’t work out of the box, and the http library it uses won’t work either. There are solutions to this within AppEngine (caching in datastore, using the support http lib) but it presents an obstacle to getting started.
- Rate limiting. Some APIs (include Twitter) limit the client IP to a certain number of request every hour. Usually you’ll have you own IP on the server, but with GAE you’re sharing your IP with others. This means that someone else on the platform could be wasting away your precious few requests. (For Twitter, of course, rate limiting is done both on IP- and account-level. So sending requests with your username/password credentials will solve the problem.)
Other than that Google AppEngine is a beautiful platform ;-)