Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Thu, 12 May 2011 17:56:47 +0000 (UTC)
From: "Dipesh Patel (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <1377973331.7486.1305223007490.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COUCHDB-904) No method to detect view server VM
 version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dipesh Patel commented on COUCHDB-904:
--------------------------------------

@Paul

Cool I think I've implemented what you originally envisioned when creating this ticket. If not let me know. There may still be some issues :S

Thanks for the feedback guys.

Dip

> 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