Rapid component dev with Couch

Colin Clark colin.clark at utoronto.ca
Tue Jul 21 22:00:15 UTC 2009


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




More information about the fluid-work mailing list