[
https://issues.apache.org/jira/browse/COUCHDB-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13648406#comment-13648406
]
Benoit Chesneau commented on COUCHDB-1743:
------------------------------------------
I know about ios. I am actually using another implementation of the view
server. Ironically while asynchronous behind it is still synchronous for
couchdb.
I disagree with "CouchDB already achieves this with JSON as the fundamental
unit of transportation. " It is actually really costly, especially since we are
storing binaries. Also I' mot sure that JSON is the best protocol ever for such
things. Anyway I specifically want to remove the steps:
Get binary
Encode to json string
send
receive
decode to json
do a thing
encode to json string
send
receive
decode
do a thing
store it
stdio means stdin/stdout so not so much over the network. I specifically intent
the possible usag e of unix/tcp sockets or any other transports if needed. The
reason is that sometimes depending on the need you may want to the calculation
at another level or on another machine.
Data between a // or not view server doesn't change the thing that at the end
the data need to be written on the disk. So again having a // implemtation of
the view server or not doesn't change anything to the couchdb internals.
couchdb only have to p[ass the data to the vies server and provide a way to
write them.
I read it, but it doesn't answer to the drawbacks I expose. I agree that each
messages could be tagged (taskid) but that doesn't imply a // implementation.
It can be used for another usage.
Can you put your proposal on the wiki so we could play with it eventually?
> 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
