Yes, the couchapp is awesome , but it seems that there is a difficulty to handle big size attachments via the REST API and submitting files by a form , must add a backend or is there a good way to do this process or it isn't suitable for the task
Luca Matteis <[email protected]>编写： >I don't think Couch is just a database server. Lots of its power comes >from the fact that you can build CouchApps with it, therefore you can >let it handle things such as the presentation layer. > >I think this is an essential component of CouchDB and we should >nurture this capability, by considering adding new functionalities, >and not ignore it by saying "just use CouchDB as a regular database >server" or "just use a proxy in front of your couch to handle that". > >Luca > >On Tue, May 29, 2012 at 4:35 PM, Keith Gable <[email protected]> >wrote: >> Also, I have to say... not every app is best suited as a CouchApp. But >> nothing stops you from writing your application in { Rails | | Sinatra | >> Django | Pylons | .NET } with CouchDB as your data store. I personally >> prefer it this way, as I tend to think of CouchDB as a database server, and >> IMHO, database servers should never handle the presentation layer. (This >> applies for RDBMSes too. I shouldn't be able to execute a SQL query and get >> back CSV, JSON, XML, etc.) >> >> --- >> Keith Gable >> A+ Certified Professional >> Network+ Certified Professional >> Storage+ Certified Professional >> Mobile Application Developer / Web Developer >> >> >> >> On Tue, May 29, 2012 at 1:40 AM, Luca Matteis <[email protected]> wrote: >> >>> I know this is also solved by putting some sort of firewall before >>> Couch. But these are little fixes and little things that could really >>> make writing couchapps a lot better.
