couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1931) documentation on shows and lists in misleading
Date Fri, 15 Nov 2013 10:55:20 GMT


Benoit Chesneau commented on COUCHDB-1931:

mm no it wasn't the core motivation . it was about sending results yes, but this is done by
transforming the doc.

Also you only see one use of the shows and lists in your text. Have a look around, ask to
some of the cloudant customer and you will see that some people are using them for other cases.
I can say for sure that if it would be only for this need a simple ajax request is enough
today for that. The interest of using lists is to have a use of the params on server side
and make sure you send the same results to all the clients. browsers or not.

The performance issue is workable, we are discussing it since awhile. I don't see why people
are using it as an argument against the use of them. If there is a performance issue and people
have some use of the lists or if it makes the lists more useful, then we should work on it.
But I don't see why we should take the performance pretext to remove or advise against them.

> documentation on shows and lists in misleading
> ----------------------------------------------
>                 Key: COUCHDB-1931
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Benoit Chesneau
> The doc says for the shows:
> {quote}
> Show functions are used to represent documents in various formats, commonly as HTML page
with nicer formatting. They can also be used to run server-side functions without requiring
a pre-existing document.
> {quote}
> and later for the lists:
> {quote}
> While Show functions are used to customize document presentation, List functions are
used for same purpose, but against View functions results.
> {quote}
> We shouldn't speak of rendering or not only. Shows are about transforming the results
depending on the parameters you pass on the URL. Rendering is just one of the possibilities
due to the ability of transforming and editing the result(s). 
> We should make it more clear.

This message was sent by Atlassian JIRA

View raw message