couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-904) No method to detect view server VM version
Date Thu, 12 May 2011 09:50:47 GMT


Alexander Shorin commented on COUCHDB-904:

Yes, a little incorrect(: 
Ok, I'll explain more  detail.  Imagine that I'm developer of some view server. I'd like to
create view server which covers most of CouchDB releases. Each new CouchDB release brings
new features, improvements and API changes, some times backward-incompatible (as for 0.9->0.10->0.11->0.11.1)
. However, I couldn't solve this task due to there is not way to know about CouchDB version
and API that I have to implement. So there are three ways that I have: 
1. develop only "bleeding edge" view server that support only latest version
2. make separate branch per version
3. keep "all in one" and pass version as command line argument. 
First one makes to forgot about old releases, second is supporting hell. Last one is more
effective, but requires to keep in mind changing argument on server update. 

So CouchDB tells view server about his version, not view server about his.

Sorry for offtopic, just thoughts about similar idea(: or may be improvement of yours: 
CouchDB pass "version" command to view server with additional value of his version and excepts
that view server return his version back. Something like "version exchange".

> No method to detect view server VM version
> ------------------------------------------
>                 Key: COUCHDB-904
>                 URL:
>             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:

View raw message