So I'm not sure if anyone here has any thoughts on this, so I thought I'd throw it out there.
My company will soon be launching a product that mates up with Couch beautifully and we're very much leveraging CouchDB as our back end server. In fact, we're using Couch not only as the database but as the web server (hence, 'couch app'). The thing is that, given that we're an all-JavaScript shop, we're not using the 'couchapp' Python script and we found the 'couchapp' NodeJS module too limited (and frankly, too buggy) for our use, so we have our own server-side JS command line tools for uploading and maintaining the app in CouchDB. But we're still "launching" the app right out of CouchDB, just like these other scripts allow you to do. The terminology I have been using for this is "Couch-served application" so that folks don't get confused with 'couchapp', the Python or JS script that is a specific implementation. I know there are other products out there that do similar things to ours. Does the term 'Couch-served app' make sense to folks and should we be using it this broader context or does someone have a better suggestion? Thanks for your input! Cheers, - Bill
