couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-904) No method to detect view server VM version
Date Mon, 09 May 2011 21:08:03 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030898#comment-13030898
] 

Alexander Shorin commented on COUCHDB-904:
------------------------------------------

I think that the main problem is quite opposite - how view server get to know with what CouchDB
server version it works? That could allows to control implemented features and their behavior
from release to release, especially if there would be a major API changes (as it was with
list function) without worry about view server "correct" version (just keep it up to dated).

> No method to detect view server VM version
> ------------------------------------------
>
>                 Key: COUCHDB-904
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-904
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>            Reporter: Paul Joseph Davis
>            Priority: Minor
>         Attachments: patch.txt
>
>
> There's currently no way to tell what version of the view server is being used. Ie, the
JS VM (Or Python, or Ruby, etc) that is being used. Just occurred to me it could be useful
for debugging things that work one place and not another.
> A proposed simple fix would be to have the view server protocol dictate that when a server
boots up it spits out a line like:
> {"version": OPAQUE_STRING} that gets stored in a view_server_versions section in the
config or some such.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message