What I am pointing out is that if you want federation then you need to design your protocols and APIs RESTfully, in this particular case it is the idea of hypertext, link following, in the AtomPub spec that allows these two separate services to be linked together.
Comments
On August 3, 2008 11:03 AM, Stefan Tilkov
said:
said:
Thanks, fixed the link.
Which feed are you referring to? Atom or RSS?
On August 3, 2008 11:15 AM, Stefan Tilkov
said:
said:
OK, see it now; yes, if what you are referring to are the Atom entry IDs in the Atom feed, they have the form “tag:www.innoq.com,2008:/blog/st/3.2717”, so they look a little like URIs, but aren’t. These are unique IDs for the entries that stay constant even if the URI changes; they seem perfectly valid, in line with the Atom spec and are, in any case, generated by MovableType. There is a link rel=’alternate’ type=’text/html’ that points to the entry’s URI. Seems fine to me - or am I missing something?
On September 29, 2009 9:11 AM, Skumar
said:
Written my thoughts on REST + Cloud offerings http://saurabhkaushik.wordpress.com/2009/09/27/cloud-is-for-rest-of-the-world/
first off, the quote link is 404
secondly, youre using TAG URIs for your post in the feed.
if you hadnt noticed, theyre incompatible with the idea of hypertext as you cant click on them and get anywhere