Return-Path: Delivered-To: apmail-avro-dev-archive@www.apache.org Received: (qmail 85115 invoked from network); 13 Jul 2010 22:12:02 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Jul 2010 22:12:02 -0000 Received: (qmail 24896 invoked by uid 500); 13 Jul 2010 22:12:01 -0000 Delivered-To: apmail-avro-dev-archive@avro.apache.org Received: (qmail 24820 invoked by uid 500); 13 Jul 2010 22:12:01 -0000 Mailing-List: contact dev-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@avro.apache.org Delivered-To: mailing list dev@avro.apache.org Received: (qmail 24812 invoked by uid 99); 13 Jul 2010 22:12:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 22:12:01 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 13 Jul 2010 22:11:58 +0000 Received: (qmail 82263 invoked by uid 99); 13 Jul 2010 22:11:36 -0000 Received: from localhost.apache.org (HELO [192.168.42.217]) (127.0.0.1) (smtp-auth username cutting, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jul 2010 22:11:36 +0000 Message-ID: <4C3CE498.1070607@apache.org> Date: Tue, 13 Jul 2010 15:11:36 -0700 From: Doug Cutting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100527 Thunderbird/3.0.5 MIME-Version: 1.0 To: dev@avro.apache.org CC: coolwhy@gmail.com Subject: Re: NettyServer initialization References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 07/13/2010 02:57 PM, Patrick Linehan wrote: > Would > you accept a patch to instead perform the initialization in the constructor? This sounds like a reasonable change to me. Please file an issue in Avro's Jira bug database and attach a patch file there. Thanks, Doug