Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <28999964.58191271182856390.JavaMail.jira@thor>
Date: Tue, 13 Apr 2010 14:20:56 -0400 (EDT)
From: "Ning Tan (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Updated: (COUCHDB-735) Support HTTP POST for the change
 notification filter API
In-Reply-To: <14974696.58031271182744760.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ning Tan updated COUCHDB-735:
-----------------------------

    Attachment: changes_filter_with_post.patch

1. Change to enable HTTP POST for changes (filter) API.
2. Futon test case.

> Support HTTP POST for the change notification filter API
> --------------------------------------------------------
>
>                 Key: COUCHDB-735
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-735
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.11
>            Reporter: Ning Tan
>         Attachments: changes_filter_with_post.patch
>
>
> Currently the change notification filters only support HTTP GET. This limits their usefulness for cases where the filter criteria passed in exceed URL query length limitations. If the API supports HTTP POST, the filter function can then inspect the BODY of the request for filtering criteria.
> I started a discussion on the mailing list here: http://mail-archives.apache.org/mod_mbox/couchdb-user/201004.mbox/browser. Chris suggested that I modify the change API to support POST (in the Erlang code) myself as an experiment. I was able to verify that the filter function was able to see the BODY of the request. However, the changes feed (with the filtering function) hangs whenever there is a BODY in the request (for both GET and POST verbs).
> I'm attaching a patch that contains the change Chris proposed as well as the updated Futon JavaScript test file for the changes API. The test currently times out (and fails). It should work once the feature is implemented.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira