﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Seb commented on Designing a document database: Remote API &amp; Public API</title><description>Or you could simply use OpenRasta...
  
  
That said, there is no such thing as an addressing scheme or predefined URIs in ReST. If you doucment what APIs to document with, that's a ReST smell. :)
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment10</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment10</guid><pubDate>Wed, 01 Apr 2009 18:48:24 GMT</pubDate></item><item><title>kyle commented on Designing a document database: Remote API &amp; Public API</title><description>Probably just same order response of the ids. 
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment9</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment9</guid><pubDate>Fri, 20 Mar 2009 20:46:27 GMT</pubDate></item><item><title>Taras commented on Designing a document database: Remote API &amp; Public API</title><description>Addressing schemes to consider:
  
  
JsonQuery: [ 
[www.sitepen.com/.../jsonquery-data-querying-bey...](http://www.sitepen.com/blog/2008/07/16/jsonquery-data-querying-beyond-jsonpath/) ]
  
  
Astoria: [ 
[msdn.microsoft.com/en-us/library/cc668766.aspx](http://msdn.microsoft.com/en-us/library/cc668766.aspx) ]
  
  
Google APIs (all of them more or less revolving around the same format): [ 
[code.google.com/p/pyrfeed/wiki/GoogleReaderAPI](http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI) ]
  
  
Implementations of document dbs:
  
- SimpleDB
  
- NSimpleDB
  
- CoachDB
  
- Persevere
  
  
Miscelanea :-)
  
- spot a mistake regarding Astoria in Dare's article: [ 
[www.25hoursaday.com/.../...InARESTfulProtocol.aspx](http://www.25hoursaday.com/weblog/2007/07/13/GoogleBaseDataAPIVsAstoriaTwoApproachesToSQLlikeQueriesInARESTfulProtocol.aspx) ]
  
- yours truly is dreaming about exposing NH repository via universal web service: [ 
[n2.codeplex.com/Thread/View.aspx?ThreadId=28810](http://n2.codeplex.com/Thread/View.aspx?ThreadId=28810) ]
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment8</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment8</guid><pubDate>Wed, 18 Mar 2009 08:39:28 GMT</pubDate></item><item><title>Bunter commented on Designing a document database: Remote API &amp; Public API</title><description>Ayende, I'm sure you have read it: 
[roy.gbiv.com/.../rest-apis-must-be-hypertext-dr...](http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven)  
  
I know, so much semantic buzz is around rest it makes people unrest, but I think the main concept (i.e. browsable API with single entry point)  of representational state transfer missies many.
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment7</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment7</guid><pubDate>Tue, 17 Mar 2009 20:58:01 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Remote API &amp; Public API</title><description>Bunter,
  
documents are resources
  
uniquely addressable by their id
  
There are cachable, stateless and layered
  
  
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment6</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment6</guid><pubDate>Tue, 17 Mar 2009 16:38:01 GMT</pubDate></item><item><title>Bunter commented on Designing a document database: Remote API &amp; Public API</title><description>Hmm, where is the representational state transfer in that api ? :)
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment5</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment5</guid><pubDate>Tue, 17 Mar 2009 10:52:24 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Remote API &amp; Public API</title><description>Configurator, 
  
Yes, delete should work
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment4</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment4</guid><pubDate>Tue, 17 Mar 2009 09:51:52 GMT</pubDate></item><item><title>configurator commented on Designing a document database: Remote API &amp; Public API</title><description>How about delete? Would you use an HTTP DELETE or a POST to a delete url?
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment3</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment3</guid><pubDate>Mon, 16 Mar 2009 23:34:10 GMT</pubDate></item><item><title>Ayende Rahien commented on Designing a document database: Remote API &amp; Public API</title><description>Josh,
  
Probably just same order response of the ids.
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment2</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment2</guid><pubDate>Mon, 16 Mar 2009 18:39:02 GMT</pubDate></item><item><title>josh commented on Designing a document database: Remote API &amp; Public API</title><description>I see.. some REST like API. Do you care if you get the correlated ID back from a POST to /bulk_docs? If so, then do you assume a reply in the same order, or allows the client to specify the ID, or return the whole post content with ID's added?
</description><link>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment1</link><guid>http://ayende.com/3911/designing-a-document-database-remote-api-public-api#comment1</guid><pubDate>Mon, 16 Mar 2009 18:10:21 GMT</pubDate></item></channel></rss>