> > Before doing any changes to view server protocol, I would prefer to > start working on a better implementation of js insde CouchDB. The > current implementation (ie using one os process for each call/request > ) even limited in a pool of process limit what you can do for obvious > reason. >
What limitations do you mean? I don't think the view server should ever *block* on anything other than processing and should still be forbidden from doing IO. We do need to implement a non-blocking line protocol for external processes and maybe some better support for a long term generic changes listener but allowing the view server to go off and do IO is an *incredibly* bad idea. > > I would prefer that we start working on a js implementation using an > erlang driver or nif (erlang_js or emonk) that would allow us to add > any needed command using erlang. So we could do what nodejs do with > its own library more easily (ie adding features in pure js but using > erlang call). One other advantage of such implementation is speed, we > won't need to pass messages in json and such, also it could be > eventually in the future distributed. > > - benoit >
