Re: Sending post request from Django to Couchdb remote server

CouchDB is meant to be used RESTfully, so go ahead and create those POST requests. That said, there are several Django backends that will help you to communicate with CouchDB but this might be more trouble than it's worth. It all depends on what you need from CouchDB. Personally I'd forego any wrappers and just use it directly. You sacrifice some of the flexibility and power of CouchDB by hiding behind Django's RDBMS-centric backend.

If you're worried about security, which is really only an issue if you choose to expose the CouchDB server to the Internet, then go ahead and look into the various authentication options offered by CouchDB. However, if it's just eavesdropping you're worried about, you can configure your CouchDB server to use SSL and limit its connections to those originating from your server only.

On Wednesday, 29 August 2012 00:33:20 UTC-4, psychok7 wrote:

So, i have a fully operational django project with postgresql to manage its contents.   Nevertheless i decided to create a second database using couchdb to keep just one part of that data. Should i use *urllib2* and send post requests to my couchdb to save the new data or this is just bad programming (not secure,etc) and i should use something else?

Thanks

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/gSZSnfoVta4J.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.