What about these scenarios: 1. I have a web 2.0 GUI based application where a user can create some content by pushing buttons and writing snippets of code -- the end result is stored as text -- and then saved to the database. 2. I want the user to be able to list their files, edit them, then resave them -- all from the web 2.0 interface.
or 1. I have a web 2.0 application where users input the vitamins levels they take vs their symptom levels for each day. Each day they can input their own symptom descriptions and values like 1 to 10. 2. When prompted, the system grabs all their data and runs statistics on it in javascript. In each case I want to do authentication -- like login/session/signup. That kind of thing. The web 2.0 GUI interfaces for both these projects involve 1000's of lines of javascript from different libraries, and multiple graphic image sets for the GUI, all of which are changing all the time during the development process. How is couchdb used in these scenarios. Right now I'm trying to get it working with couch.js but running into the cross domain problem. I can't send anything from an html page into the :5984 port. Thanks, Dan -----Original Message----- From: Randall Leeds <[email protected]> To: [email protected] Sent: Thu, Aug 19, 2010 4:42 pm Subject: Re: reverse proxy discouraged? I think for your use case a reverse proxy is fine, especially if the 'web2.0' content is a server itself running python/ruby/perl/java/erlang/scala/node/insert/favorite/middleware/here At which point you likely don't even need to expose couch to the outside at all. Just put it in your private network and access it from your application server. Exposing couch directly to the world via a reverse proxy is probably only a good plan if you need to co-host a public couch with other apps or static files behind different virtual hosts or if you want to do complicated authentication in front of your couch that couchdb can't do itself. -Randall On Thu, Aug 19, 2010 at 15:41, <[email protected]> wrote: > Is using a reverse proxy to serve up html and couchdb from the same domain > and port problematic? > Someone told me that it is highly discouraged > > and that html pages should be served from couchdb. > But on a site that is web 2.0 and has a complicated GUI there would need to > be 100's of attachments that would be necessary to correctly > serve up a page as an attachment to a document. > > This sounds unreasonable for development where 100's of changes are made per day. > > The reverse proxy method seems feasible but why would it be discouraged? > > Thanks, > > Dan > > > > > > > >
