Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C21C10290 for ; Wed, 14 Jan 2015 22:49:08 +0000 (UTC) Received: (qmail 48923 invoked by uid 500); 14 Jan 2015 22:49:09 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 48860 invoked by uid 500); 14 Jan 2015 22:49:09 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 48847 invoked by uid 99); 14 Jan 2015 22:49:09 -0000 Received: from tyr.zones.apache.org (HELO tyr.zones.apache.org) (140.211.11.114) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jan 2015 22:49:09 +0000 Received: by tyr.zones.apache.org (Postfix, from userid 65534) id E8D90A42F33; Wed, 14 Jan 2015 22:49:08 +0000 (UTC) From: mikewallace1979 To: dev@couchdb.apache.org Reply-To: dev@couchdb.apache.org References: In-Reply-To: Subject: [GitHub] couchdb-couch pull request: Add a configurable timeout for get_pro... Content-Type: text/plain Message-Id: <20150114224908.E8D90A42F33@tyr.zones.apache.org> Date: Wed, 14 Jan 2015 22:49:08 +0000 (UTC) Github user mikewallace1979 commented on the pull request: https://github.com/apache/couchdb-couch/pull/31#issuecomment-70008468 > get_proc_timeout is good name for internals, but for configuration it should be more user friendly and explain what exactly it controls. Exposing knowledge of gen_server calls to user level configs doesn't simplifies all the things I agree but I couldn't figure out a better name given that it is pretty much only an internal gen_server concern. Will ponder some more. Maybe it's a sign that exposing it externally is a Bad Idea. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---