make the view_changes API more simple

[benoitc]

Actually the view changes api in #1 imply to add the option seq_indexed: true to either design doc options to get view changes without the view arguments:

{
    "_id": "_design/test",
    ...

    "options": {
        "seq_indexed": true
    }
}

or view options to filter the view by key, start_key or end_key:

{
    "_id": "_design/test",
    ...

    "views": {
        "someview": {
            "map": "function(doc) { emit(null, doc); }",
            "options": {
                "seq_indexed": true
            }
        }
    }
}

Which complicate a little the API for little benefice imo. The main benefice is to reduce the disk usage by only indexing needed views. I'm thinking to simplify the API by using only one global design doc options seq_indexed: true . Then we could:

• either index each views (one seq btree / view) like the seq_indexed: true options applied to a view gave
• or do this filtering only in memory by streaming all results in a view which would be less efficient for ranges & key queries but would use less disk by only requiring a view group index (one index for all the design document).

Thoughts?

[benoitc]

applied in last head