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

Dale Harvey commented on COUCHDB-1089:
--------------------------------------

Caolan, do you mean expose the filter options on the (remote) target db that 
you are replicating too? I can see where that can be handy but I do think it 
sounds dangerous.

Kowsik, if require_valid_user does what I think it does then it wont be 
affected, a private install will stay private.

Filipe, the futon replication page is ok enough as a db admins tool, we are 
talking about providing a ui to replication for end users of applications built 
with couch (more specifically in my case, couchapps), right now its impossible 
for me to have continuous replication for my mobile apps because the user the 
app runs as is not an admin, I can start continous replication tasks but cant 
inspect whether they are running or not.

> 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

Reply via email to