Comments on: Off the Shelf Integration in Enterprises http://simonmcmanus.wordpress.com/2008/02/21/off-the-shelf-integration-in-enterprises/ Tue, 03 Mar 2009 15:02:57 +0000 http://wordpress.com/ hourly 1 By: Morethanseven » Sorry, but the Flickr API isn’t REST http://simonmcmanus.wordpress.com/2008/02/21/off-the-shelf-integration-in-enterprises/#comment-1051 Morethanseven » Sorry, but the Flickr API isn’t REST Thu, 21 Feb 2008 22:50:40 +0000 http://simonmcmanus.com/?p=186#comment-1051 [...] one about the difference between mashups and integration. All good fun basically. Simon also had an interesting take on the topic as [...] [...] one about the difference between mashups and integration. All good fun basically. Simon also had an interesting take on the topic as [...]

]]> By: Gareth http://simonmcmanus.wordpress.com/2008/02/21/off-the-shelf-integration-in-enterprises/#comment-1050 Gareth Thu, 21 Feb 2008 20:07:47 +0000 http://simonmcmanus.com/?p=186#comment-1050 My take was really that mashups vs integration is a context thing. I actually think it's not that mashups are fun, but that if it's fun you're more likely to call it a mashup. Here's a good one: what would you call work that involved making flickr talk with sharepoint? Do both ends need to be nice and/or fun for it to be a mashup? Oh (pedant alert), and neither Twitter or Flickr are RESTful. Flickr is a good old fashioned RPC API - just a lovingly documented and well designed in most places one. Twitter is what you get if you use Rails, which is in my view better but broken in a couple of important places (check out the destroy method if you don't believe me). My take was really that mashups vs integration is a context thing. I actually think it’s not that mashups are fun, but that if it’s fun you’re more likely to call it a mashup.

Here’s a good one: what would you call work that involved making flickr talk with sharepoint? Do both ends need to be nice and/or fun for it to be a mashup?

Oh (pedant alert), and neither Twitter or Flickr are RESTful. Flickr is a good old fashioned RPC API – just a lovingly documented and well designed in most places one. Twitter is what you get if you use Rails, which is in my view better but broken in a couple of important places (check out the destroy method if you don’t believe me).

]]>