On Sep 17, 12:00 pm, Paul Downey <[email protected]> wrote: > On Fri, Sep 17, 2010 at 10:47 AM, FND <[email protected]> wrote:
> > Unfortunately, it doesn't seem like we can imitate TiddlyWeb's API > > without additional middleware. > > It would be interesting to understand what those issues are, and if > they are related to Couch orhttp://www.couchone.com/hosting. > To clarify when FND talks about imitating the TiddlyWeb API here it was with the hope that client side code written to work with TiddlyWeb could be used with CouchDB as well. The issues we ran into in this regard are related to CouchDB itself and not to the hosting - until this morning we've been working on a local install of the couchdb trunk. For instance CouchDB has certain required fields for documents (_id and _rev) which differ from what is used in the TiddlyWeb API. The API endpoints (URLs) are also different. While CouchDB's url rewriter gives us some flexibility here it is limited in what it can do. Accurately implementing the TiddlyWeb API endpoints for bags, recipes and json representations of tiddlers would also require some middleware (or possibly some .htaccess magic). CouchDB does not provide revisioning that we can use out of the box and while it can be implemented it would involve multiple requests to the server when saving a tiddler. Furthermore there's the issue of implementing bags, recipes, search and filters where we'd possibly run into limitations with how much can be done with a single view function no matter how creatively written (i.e. we might need multiple requests to the server to get the desired data)... though it is possible some map/reduce ninja might prove me wrong here. Saq -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
