[jira] Commented: (COUCHDB-448) Support Gzip encoding for replicating over slow connections
[ https://issues.apache.org/jira/browse/COUCHDB-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005659#comment-13005659 ] Colin Godsey commented on COUCHDB-448: -- This should be a configurable option for all HTTP requests, as deflate/gzip is an HTTP standard, and quite useful when pushing large json documents over the internet. Compressed json is still faster than most serialization methods, and pretty dense too. Support Gzip encoding for replicating over slow connections --- Key: COUCHDB-448 URL: https://issues.apache.org/jira/browse/COUCHDB-448 Project: CouchDB Issue Type: Improvement Components: HTTP Interface Reporter: Jason Davies Assignee: Adam Kocoloski This shouldn't be too hard to add, we should support it in general for all HTTP requests to the server and also allow it to be enabled in the replicator client for pull/push replication. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-1089) Let anonymous users access _active_tasks for view generation estimates
[ https://issues.apache.org/jira/browse/COUCHDB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005985#comment-13005985 ] Dale Harvey commented on COUCHDB-1089: -- I have also really wanted this I found it extremely strange that instantiating a replication was possible without admin credentials but its never possible to see its status, im happy to provide a patch if the feature is agreeable 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
[jira] Created: (COUCHDB-1090) jquery.couch.js enforces cache option
jquery.couch.js enforces cache option - Key: COUCHDB-1090 URL: https://issues.apache.org/jira/browse/COUCHDB-1090 Project: CouchDB Issue Type: Bug Components: Infrastructure Reporter: Dale Harvey Priority: Trivial jquery.couch.js explicitly sets a cache, preventing the programmer from being able to set it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (COUCHDB-1090) jquery.couch.js enforces cache option
[ https://issues.apache.org/jira/browse/COUCHDB-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey updated COUCHDB-1090: - Attachment: cache.patch jquery.couch.js enforces cache option - Key: COUCHDB-1090 URL: https://issues.apache.org/jira/browse/COUCHDB-1090 Project: CouchDB Issue Type: Bug Components: Infrastructure Reporter: Dale Harvey Priority: Trivial Attachments: cache.patch jquery.couch.js explicitly sets a cache, preventing the programmer from being able to set it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (COUCHDB-943) Reformat comments with type specs and @doc directives
[ https://issues.apache.org/jira/browse/COUCHDB-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Harvey closed COUCHDB-943. --- Resolution: Not A Problem Too old too apply, better done while developing anyway Reformat comments with type specs and @doc directives - Key: COUCHDB-943 URL: https://issues.apache.org/jira/browse/COUCHDB-943 Project: CouchDB Issue Type: Bug Components: Documentation Reporter: Dale Harvey Priority: Minor Attachments: format_comments.patch Start introducing consistent use of @doc directives and type specifications, makes it easier to use dialyzer and ensures the comments show up in generated documentation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-1089) Let anonymous users access _active_tasks for view generation estimates
[ https://issues.apache.org/jira/browse/COUCHDB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13005988#comment-13005988 ] kowsik commented on COUCHDB-1089: - Bad idea. I've got a bunch of Couch's on EC2 and *do not* want anyone to access anything on these Couch's. I have the require_valid_user set to true with the assumption that everything's locked down. While EC2 security groups help, I'll sleep better knowing that Couch is not going to reveal anything to anyone without the required credentials. 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
