On Tue, Jul 07, 2009 at 07:44:15PM +0200, Stream Service || Mark Scholten wrote: > - 1 instance for multiple databases (not an instance per database)
This already happens. That is, if you do operations to http://yourserver/firstdb/... and http://yourserver/seconddb/... then they will be two different databases, but the same couchdb instance manages them. The database filehandles are kept open up to a limit of (I think) 100. After that, the least-recently-used database is closed. But that's transparent to users, since http is stateless. Some care would be needed on a shared platform to prevent access to magic URLs at the top level like /_restart. You can set up specific proxying rules, e.g. http://yourserver/user1/* => http://localhost:5984/user1/* (with user-specific authentication for each rule) and block out access to the top level entirely.
