Comments on: Mashup presentation slides and links http://mortenjust.com/2009/03/30/mashup-presentation-slides-and-links/ Vi har Morten Just og rock og silkepapir med is i vores hjerner Thu, 29 Jul 2010 06:18:49 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Steffen Tiedemann Christensen http://mortenjust.com/2009/03/30/mashup-presentation-slides-and-links/comment-page-1/#comment-234303 Steffen Tiedemann Christensen Mon, 30 Mar 2009 13:50:48 +0000 http://blog.genstart.dk/2009/03/30/mashup-presentation-slides-and-links/#comment-234303 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 ;-) 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 ;-)

]]>