Hi Colin, thank you for picking that up and coming up with some recommendations. I will tomorrow afternoon look into the matter to be able to use CouchDB as a web server. This seems the best solution for me to keep on developing.
Thanks very much, Armin -- On Tue, Jul 21, 2009 at 18:00, Colin Clark <[email protected]> wrote: > Hey all, > > At standup today, Armin and Yura mentioned that they ran into the classic > Same Origin Policy issue when developing with plain HTML and CouchDB. Since > Couch is served up on a different port than your HTML files, the browser > will forbid the request by default. Hearing about this snag, a few potential > solutions ran through my head: lower the security level of your browser? use > JSONP and limit yourself to GET requests? use Kettle? > > The latter approach is probably our best option in the long run. But a > quick browse through the CouchDB documentation pointed me to a simple > solution for doing rapid development of Engage components: use Couch itself > as a Web server for your HTML documents. This'll keep your browser secure > and get you up and running fast. > > For more information, read up on the "Developing with CouchDB" section > here: > > http://books.couchdb.org/relax/ > > Again, this isn't a production-level solution, but it should be suitable > for getting up and running fast. > > Colin > > --- > Colin Clark > Technical Lead, Fluid Project > Adaptive Technology Resource Centre, University of Toronto > http://fluidproject.org > >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
