[ https://issues.apache.org/jira/browse/COUCHDB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006024#comment-13006024 ] 

Caolan McMahon commented on COUCHDB-1089:
-----------------------------------------

@Dale: if you find support for that patch I'd also consider exposing the filter and its parameters if a filter is used for replication. It could open up some really nice UI possiblities. Providing these details could make setting up custom sync with couchapps a user rather than an admin thing.

Also, if we decide to expose _active_tasks on a per-database level it would make sense to expose it at the root level under a vhost (much like /_session).

> Let anonymous users access _active_tasks for view generation estimates
> ----------------------------------------------------------------------
>
>                 Key: COUCHDB-1089
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1089
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface, JavaScript View Server
>            Reporter: max ogden
>            Priority: Minor
>              Labels: http, view
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> Currently you have to be a database administrator to access _active_tasks. For UX purposes I would like to allow anyone to see view generation statuses, preferably on a per database level. This solves the problem of the first user to generate a view that then receives no time estimate as to when their process will be completed. I can't think of an application use case for making replication data public.
> I spoke with Volker Mische about the implementation details on this issue and he asserted after a code dive that it appears achievable, though the innards of the view status code were not familiar to him.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira