[
https://issues.apache.org/jira/browse/COUCHDB-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hammond updated COUCHDB-377:
---------------------------------
Attachment: couch_native_process.erl
Attaching a simple native view server. I've named it couch_native_process.erl
in anticipation of it being shipped with couch itself. It is fairly
minimalistic - no 'helper' functions are provided, just a raw erlang interface.
The comments at the top of the file include the instructions for configuring
and testing, but it assumes Jan's other patch in this issue has already been
applied.
> allow native view servers
> -------------------------
>
> Key: COUCHDB-377
> URL: https://issues.apache.org/jira/browse/COUCHDB-377
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Mark Hammond
> Attachments: couch_native_process.erl, native_query_servers.patch,
> native_query_servers.patch, query_proc.patch
>
>
> There has been some discussion on IRC etc about how to support 'native' view
> servers, such as 'erlview' in a generic way. Currently using erlview
> requires you to modify couch.
> I'm attaching a patch as a first attempt at supporting this. In summary, the
> patch now looks up a new 'native_query_servers' config file section for a
> list of view_server names with a {Module, Func, Args} style string specifying
> the entry-point of the view server. The code now passes an additional atom
> around indicating if the PID is 'native' or 'external', and map_docs takes
> advantage of this to avoid the json step. This patch allows erlview to work
> for me, but in theory any erlang code could be used here.
> I'm very new at erlang - please let me know if I should make stylistic or
> other changes, or indeed if I should take a different approach completely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
