incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] Commented: (COUCHDB-441) Finally implement pre-write-doc-edit handlers.
Date Sun, 02 Aug 2009 19:55:14 GMT


Paul Joseph Davis commented on COUCHDB-441:

My original thoughts were that this would be a pretty thin wrapper that would mutate a single
document when putting. Adding the ability to work with arbitrary data and return arbitrary
responses changes the game somewhat.

I'd disagree pretty strongly with using _show because the basic intent is quite different.

The other thing I just realized is that there's also no way to use the current scheme with

Things to think about.

> Finally implement pre-write-doc-edit handlers.
> ----------------------------------------------
>                 Key: COUCHDB-441
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Curt Arnold
>             Fix For: 0.10
>         Attachments: COUCHDB-441.patch
> It would be useful for auditing to have the identity of the user who inserted a new revision
and the timestamp of the operation to be inserted in the document in the same way that the
new revision number is.
> Doing this at the application level is not adequate since it would be readily spoofable
and would bypass the authentication handler.
> There is a comment in couch_db:update_docs about generating new revision ids, but I couldn't
quite comprehend what specific code was responsible for inserting the id into the document.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message