What the HTTP is CouchApp • Hacker News Board

Re: What the HTTP is CouchApp

#21

Post by limmeau » Tue, Aug 03, 2010, 12:49 PM UTC

TomasSedovic wrote: post #20

limmeau wrote: post #19

Earlier quoted context omitted.

Great to see that feature... I only played with CouchDB in 0.7-days before shows and lists, and found it too everything-is-public for my needs. Let's suppose I want to build a centralized messaging application where users send each other private messages (and let's say per-user couches aren't available). Users may only see messages directed to them. Messages are contained in documents, one document per message (sound…

Yes that would work. You could go a bit further, though: Set your view to emit keys this way: [user,message_id] you can query the view using: msgview?startkey=[user]&endkey=[user,{}] which will give you all the messages for the given user, or msgview?startkey=[user,message_id]&limit=1 for a specific message. Then your list doesn't have to go through all the messages for all the users -- just the ones that the view re…

Thank you!

Re: What the HTTP is CouchApp

#22

Post by arturadib » Tue, Aug 03, 2010, 12:53 PM UTC

I've been waiting for this for a long time. Case in point: Feedlooks.com.

I created the entire app logic in jQuery, which is amazing for rapid app development by the way, and all that missing was an http data server.

Of course I had to build my own interface on the server side to mediate the database transfer. It's really an unnecessary layer.

Glad someone had this idea.

Re: What the HTTP is CouchApp

#23

Post by jchrisa » Tue, Aug 03, 2010, 3:31 PM UTC

limmeau wrote: post #19

TomasSedovic wrote: post #16

Earlier quoted context omitted.

A jchrisa pointed out, you can't get more granular than per-database read restriction using just CouchDB. However, you can put the database behind a proxy and use lists and shows (that get passed the user info) to restrict the read access.

Great to see that feature... I only played with CouchDB in 0.7-days before shows and lists, and found it too everything-is-public for my needs. Let's suppose I want to build a centralized messaging application where users send each other private messages (and let's say per-user couches aren't available). Users may only see messages directed to them. Messages are contained in documents, one document per message (sound…

If you want to allow the users to take the db offline, you will still be happiest giving each user or group their own database. Databases are just a file on the server, and CouchDB has been deployed with millions of databases on a single server. So the one database per user model is totally viable.

Re: What the HTTP is CouchApp

#24

Post by jchrisa » Tue, Aug 03, 2010, 3:34 PM UTC

arturadib wrote: post #22

I've been waiting for this for a long time. Case in point: Feedlooks.com. I created the entire app logic in jQuery, which is amazing for rapid app development by the way, and all that missing was an http data server. Of course I had to build my own interface on the server side to mediate the database transfer. It's really an unnecessary layer. Glad someone had this idea.

That's a lot like my last web app before I started using CouchDB. Before I made the switch I was storing JSON in text fields in Postgres. Views are much better than the hoops I had to jump through to query that.

Re: What the HTTP is CouchApp

#25

Post by jchrisa » Tue, Aug 03, 2010, 3:37 PM UTC

iamwil wrote: post #8

cmurphycode wrote: post #5

Earlier quoted context omitted.

Thank you; that is what I meant to explain, but you were much more clear. I guessed that wil was asking about the safety of his own application once replicated by others, because I don't see the concern of having users replicate their own copy, as long as the damage is contained.

Right, I was asking about the safety of the application that I write. So any app written on couchapp can be considered to be modified by the end user if it's replicated to their machine. Then any application where you don't want users fiddling around with your 'source' is out of the question. That said, there's plenty of applications that you'd want to pass along with the user's own data that you'd want the end users…

Validation funs give you a lot of control over the update logic. However, they cannot be used to grant anonymous write access to application code. The design document may only be updated by the database or server admin.