[
https://issues.apache.org/jira/browse/COUCHDB-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson updated COUCHDB-209:
-----------------------------------
Fix Version/s: (was: 0.9)
0.10
Priority: Major (was: Blocker)
Issue Type: Wish (was: Improvement)
I think I agree with Paul - I'm not exactly sure what I'd change here...
I think this may be tied up in the larger refactor of show/list and
OTPification of CouchDB into different applications. I'm moving this ticket
from 0.9
If you're using _external and you have a concrete proposal (for how you'd like
configuration to be different, please attach a well-commented ini file that
illustrates the difference between how it is now, and how you'd like it to be.)
Maybe this ticket is just asking for something simple, but I'm having a hard
time wrapping my head around exactly what.
> Refine httpd_db_handlers API to map the externals from paths directly to
> scripts
> --------------------------------------------------------------------------------
>
> Key: COUCHDB-209
> URL: https://issues.apache.org/jira/browse/COUCHDB-209
> Project: CouchDB
> Issue Type: Wish
> Components: HTTP Interface
> Affects Versions: 0.9
> Environment: all
> Reporter: Jeff Hinrichs
> Assignee: Chris Anderson
> Fix For: 0.10
>
>
> We could change the API to map the externals from paths directly to
> scripts, like
> [httpd_db_handlers]
> _mypath = {couch_httpd_external, handle_external_req, "/path/to/my/script"}
> which would be fine by me.
> The current code is like it is because the original implementation was
> designed to have multiple scripts mounted at the /db/_external path.
> Do you mind opening a ticket about this? - I'm happy to write the code
> but I'm supposed to be working on the book right now, so it'll have to
> wait.
> link to mail list thread:
> http://mail-archives.apache.org/mod_mbox/couchdb-user/200901.mbox/%[email protected]%3e
> It would appear to be a good solution to allow the flexibility desired while
> narrowing the number of local.ini edits to accomplish.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
