On May 28, 2012, at 2:26 PM, Luca Matteis wrote:
contained in the request), so why not give the IP address of the
request as well? This would allow the creation of even more powerful
Couchapps.
The IP address is not very useful for what you're trying to do. Given the
prevalence of NAT (even by
Yes, people could get around the voting by simply using a proxy server
or logging in from somewhere else. But the idea is that it makes it
*harder* for people to vote based on their IP address.
Also there's an issue that I'm having with my Couchapp which is that
it's extremely easy for users to
After thinking about this spam issue, I realized that there's really
no accurate way of circumnavigating this issue.
As you say, people can very easily change their IP address, therefore
I changed my mind and I don't think this is a very useful feature
anymore.
Thanks for making things more clear
Hi all,
I'm exploring couchdb, and I'd like to know how can I use as
front-end also.
So I think I need to disable the reading of some document to some
users/roles/groups.
Is this possible? Or have I to use a different front-end?
Thanks
Alessandro
Hi,
While you'd like to disable GET for some users for some doc with _id:
foo he could alternatively get it via:
curl -X POST http://localhost:5984/db/_all_docs?include_docs=true -d
'{keys:[foo]}' -H Content-Type: application/json
Same works for other views. Probably, per-user db or
On 29 May 2012 13:29, Alessandro dedalus2...@gmail.com wrote:
Hi all,
I'm exploring couchdb, and I'd like to know how can I use as front-end
also.
So I think I need to disable the reading of some document to some
users/roles/groups.
Is this possible? Or have I to use a different
Thanks to you all!
It is clear, I have to use a front-end in order to manage a low level
documents privileges.
Alessandro
Also, I have to say... not every app is best suited as a CouchApp. But
nothing stops you from writing your application in { Rails | | Sinatra |
Django | Pylons | .NET } with CouchDB as your data store. I personally
prefer it this way, as I tend to think of CouchDB as a database server, and
IMHO,
I don't think Couch is just a database server. Lots of its power comes
from the fact that you can build CouchApps with it, therefore you can
let it handle things such as the presentation layer.
I think this is an essential component of CouchDB and we should
nurture this capability, by considering
Yes, the couchapp is awesome , but it seems that there is a difficulty to
handle big size attachments via the REST API and submitting files by a form ,
must add a backend or is there a good way to do this process or it isn't
suitable for the task
Luca Matteis lmatt...@gmail.com编写：
I
On May 17, 2012, at 10:05 PM, Adam Kocoloski wrote:
On May 17, 2012, at 9:50 PM, Jens Alfke wrote:
FYI, the person who reported this issue to me was running a CouchDB 1.0
server, not BigCouch. He says it went away after he upgraded to CouchDB 1.2.
That implies that the 'encoding' and
11 matches
Mail list logo
