[
https://issues.apache.org/jira/browse/COUCHDB-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648399#comment-13648399
]
Samuel Williams commented on COUCHDB-1743:
------------------------------------------
Hi Benoit.
1/ We'd be totally screwed on iOS even with the current implementation. I'm
simply trying to suggest that we have a 1-to-1 mapping between design documents
and processes. This could be, for example, 1-to-1 mapping between threads and
design documents. At present, my understanding is that processes can be reused
for multiple design documents which is something I fundamentally disagree with.
2/ Agreed, designing a protocol in a more generic fashion is a great idea,
however I believe CouchDB already achieves this with JSON as the fundamental
unit of transportation. There are many different wire-level serialisation
options.
3/ I'm not the one suggesting to base decisions of performance at this point,
however I do agree performance needs to be considered, e.g. the considerations
in my proposal document at present.
4a/ Agreed, too much overhead.
4b/ Not sure I understand what you are suggesting here. stdio can go over
network if required, but the latency might be a problem.
4c/ Addressed in my proposal to some extent.
4d/ Disagree. The data flow is fundamentally different and in addition, a non
parallel view server might be managed differently from a parallel one. e.g. you
might instantiate multiple view servers for the same design document.
5/ Agreed. Why don't you read my proposal document?
> Make the view server & protocol faster
> --------------------------------------
>
> Key: COUCHDB-1743
> URL: https://issues.apache.org/jira/browse/COUCHDB-1743
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Dave Cottlehuber
> Labels: couchdb, erlang, gsoc2013, html, javascript, nodejs, rest
>
> View server protocol enhancements/refactoring - unix sockets, pipelining,
> different wire format etc. Faster!!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
