[
https://issues.apache.org/jira/browse/COUCHDB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892713#action_12892713
]
Filipe Manana commented on COUCHDB-837:
---------------------------------------
Seems it's hard to reach an alternative that everyone likes :(
My personal preferences:
1) Like Chris said, this would be the behaviour of stale=ok (let the view
update run on background after serving the client) - big advantage - there's no
new query parameter nor value. I don't see any problem with it;
2) Add new value to the stale option (so far I like "lazy" or "once")
> Adding stale=partial
> --------------------
>
> Key: COUCHDB-837
> URL: https://issues.apache.org/jira/browse/COUCHDB-837
> Project: CouchDB
> Issue Type: Improvement
> Environment: all released and unreleased versions
> Reporter: Filipe Manana
> Assignee: Filipe Manana
> Attachments: stale_partial.patch
>
>
> Inspired by Matthias' latest post, at
> http://www.paperplanes.de/2010/7/26/10_annoying_things_about_couchdb.html,
> section "Views are updated on read access", I added a new value to the
> "stale" option named "partial" (possibly we need to find a better name).
> It behaves exactly like "stale=ok" but after replying to the client, it
> triggers a view update in the background.
> Patch attached.
> If no one disagrees this isn't a good feature, or suggest a better parameter
> value name, I'll commit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
