You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/07/14 14:53:45 UTC

[GitHub] eiri opened a new issue #1226: Investigate how hard could it be to reintroduce etags in index's views.

eiri opened a new issue #1226: Investigate  how hard could it be to reintroduce etags in index's views. 
URL: https://github.com/apache/couchdb/issues/1226
 
 
   We've removed etag header from views in Couch 2.0. It should be possible to construct consistent etag on fabric level, and return 304 if the etag matches the header.
   
   ## Expected Behavior
   View should return consistent Etag header. View should respect 'if-none-match' header.
   
   ## Current Behavior
   View doesn't return ETag header
   
   ## Possible Solution
   Robert Newson's idea from COUCHDB-2859 :
   
   > Here's an implementation idea that should be no more expensive than what we do today;
   > 
   >    1. delay the response until we have heard from one shard of each range (I believe we already added this, but do check)
   >    1. from this, construct the etag (we can change the workers to return more information along with their first rows (if any)
   >    1. send 304 if the etag matches the header
   
   ## References
   
      * [COUCHDB-2859](https://issues.apache.org/jira/browse/COUCHDB-2859)
      * apache/couchdb-chttpd#90
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services