You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Miles Fidelman <mf...@meetinghouse.net> on 2012/03/09 00:03:50 UTC
re:
Gregor,
Somehow I missed your posting until just now, so first off.. thanks!
minutes.io looks very interesting - thanks for the info!
Miles
On 27 February 2012 12:17, Gregor Martynus<gr...@martynus.net> wrote:
> Miles,
>
> I build minutes.io with a similar approach. You can use it when being offline, synchronization
with the couchApp backend is happening in the background.
>
> I don't think there is a library I'd recommend to use for such an architecture, not yet.
Maybe have a look at
> https://github.com/mikeal/browsercouch and https://github.com/mikeal/pouchdb
>
> I use backbone.js myself for the frontend and store all data in localStorage, which gets
synched asynchronously using _changes feed and _bulk_docs API. I also use a tiny node.js proxy
for security reasons and for some couchDB tasks like creating User Databases and Replications.
>
> I'm happy to answer any questions if you have any
>
On Thursday, 23. February 2012 at 03:10, Miles Fidelman wrote:
>
>> I'm looking at building a data management application that's essentially
>> a hybrid of an HTML5 WebApp (taking advantage of the App Cache and local
>> data storage for disconnected operation) and a CouchApp (doing fancier
>> stuff, data sharing, replication, etc. on one or more server-side
>> CouchDB installations). If you think of a collection of linked
>> spreadsheets - where each spreadsheet "lives" in CouchDB, but can be
>> cached, viewed, and edited in-browser when disconnected - you won't be
>> far off.
>>
>> My questions: Are there any good examples of applications that are
>> already doing this kind of thing? Are there any good frameworks or
>> libraries that I should be focusing on?
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra