Comments on: Why REST http://barelyenough.org/blog/2006/04/why-rest/ Tue, 06 Jan 2009 23:02:18 +0000 http://wordpress.org/?v=2.5 By: Alex http://barelyenough.org/blog/2006/04/why-rest/#comment-663 Alex Fri, 21 Apr 2006 05:42:22 +0000 http://pezra.barelyenough.org/blog/?p=225#comment-663 <p>Feedback welcome. :)</p> <p>http://feedlounge.com/blog/2006/04/20/matt-walters-release/</p> Feedback welcome. :)

http://feedlounge.com/blog/2006/04/20/matt-walters-release/

]]> By: Alex http://barelyenough.org/blog/2006/04/why-rest/#comment-642 Alex Sat, 08 Apr 2006 08:55:30 +0000 http://pezra.barelyenough.org/blog/?p=225#comment-642 <blockquote>Well, if it were really RESTful my subscription list would be a resource with a real name, say something like `http://feedlounge.com/pezra/subscriptions/opml`.</blockquote> <p>That is exactly what the API will be providing, among other things. The URL has already been determined and will be:</p> <p>http://api.feedlounge.com/username/feeds/opml</p> <p>Look for this to be available in the next week or two.</p> <p>So many features to build, so little time.</p>

Well, if it were really RESTful my subscription list would be a resource with a real name, say something like `http://feedlounge.com/pezra/subscriptions/opml`.

That is exactly what the API will be providing, among other things. The URL has already been determined and will be:

http://api.feedlounge.com/username/feeds/opml

Look for this to be available in the next week or two.

So many features to build, so little time.

]]> By: Peter Williams http://barelyenough.org/blog/2006/04/why-rest/#comment-639 Peter Williams Sat, 08 Apr 2006 03:31:49 +0000 http://pezra.barelyenough.org/blog/?p=225#comment-639 <blockquote> <blockquote> <p>Sadly, FeedLounge completely ignores web architecture.</p> </blockquote> <p>not that we don’t support REST (FeedLounge is ~99% REST)</p> </blockquote> <p>I don't know if FeedLounge is in fact ~99% REST or not. To be perfectly honest I have not really looked at the information architecture of FeedLounge beyond this the the URLs that show up in the address line (but since FeedLounge is deeply AJAX the URIs in the address line do <em>not</em> tell the whole story). So it is possible that this area is an anomily in the RESTfulness of FeedLounge.</p>

Sadly, FeedLounge completely ignores web architecture.

not that we don’t support REST (FeedLounge is ~99% REST)

I don’t know if FeedLounge is in fact ~99% REST or not. To be perfectly honest I have not really looked at the information architecture of FeedLounge beyond this the the URLs that show up in the address line (but since FeedLounge is deeply AJAX the URIs in the address line do not tell the whole story). So it is possible that this area is an anomily in the RESTfulness of FeedLounge.

]]> By: Peter Williams http://barelyenough.org/blog/2006/04/why-rest/#comment-638 Peter Williams Sat, 08 Apr 2006 03:21:12 +0000 http://pezra.barelyenough.org/blog/?p=225#comment-638 <p>Well, if it were really RESTful my subscription list would be a resource with a real name, say something like <code>http://feedlounge.com/pezra/subscriptions/opml</code>. If I attempted to GET that resource outside of an authenticated session it support HTTP based authentication (401 responses, etc). Perhaps the most important part of REST is the <em>uniform</em> interface it provides. A proprietary application specific authentication scheme is not RESTful.</p> <p>That being said I understand that providing machine readable data to the outside world is not one of <a href="http://feedlounge.com">FeedLounge</a>'s priorities. It is a user facing aggregator all, and the user experience is nice.</p> Well, if it were really RESTful my subscription list would be a
resource with a real name, say something like
http://feedlounge.com/pezra/subscriptions/opml. If I attempted to
GET that resource outside of an authenticated session it support HTTP
based authentication (401 responses, etc). Perhaps the most important
part of REST is the uniform interface it provides. A proprietary
application specific authentication scheme is not RESTful.

That being said I understand that providing machine readable data to
the outside world is not one of FeedLounge’s
priorities. It is a user facing aggregator all, and the user
experience is nice.

]]> By: Alex http://barelyenough.org/blog/2006/04/why-rest/#comment-633 Alex Fri, 07 Apr 2006 17:05:36 +0000 http://pezra.barelyenough.org/blog/?p=225#comment-633 <p>Stay tuned for some real APIs coming soon that should give you exactly what you're looking for. The problem with what you are currently trying to do is that your GET request doesn't have a n authenticated session associated with it (if it did, it would work), not that we don't support REST (FeedLounge is ~99% REST).</p> Stay tuned for some real APIs coming soon that should give you exactly what you’re looking for. The problem with what you are currently trying to do is that your GET request doesn’t have a n authenticated session associated with it (if it did, it would work), not that we don’t support REST (FeedLounge is ~99% REST).

]]>