couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (Updated) (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-1164) Pass CouchDB version to view server
Date Wed, 19 Oct 2011 22:55:11 GMT


Randall Leeds updated COUCHDB-1164:

    Fix Version/s: 2.0

As per my comment on COUCHDB-904, 2.0 seems like a good time to do this.
> Pass CouchDB version to view server
> -----------------------------------
>                 Key: COUCHDB-1164
>                 URL:
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: JavaScript View Server
>            Reporter: Alexander Shorin
>            Priority: Minor
>             Fix For: 2.0
> 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 there is actually no way to make great view server such as javascript/erlang one with
"wide" CouchDB versions support. Without that support using and developing couchapps for ruby/python/clojure/others
view servers is quite unpromising.
> This issue could be an improvement of COUCHDB-904 by using next scenario:
> CouchDB pass "version" command to view server with additional value of CouchDB version
and excepts that view server return his version back. That would be something like "version

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message