Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <2076089.122411283372334307.JavaMail.jira@thor>
Date: Wed, 1 Sep 2010 16:18:54 -0400 (EDT)
From: "Philip Zeyliger (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Subject: [jira] Commented: (AVRO-649) Allow pluggable ThreadPools in Java
 HttpServer
In-Reply-To: <23947033.120181283366217897.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AVRO-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905198#action_12905198 ] 

Philip Zeyliger commented on AVRO-649:
--------------------------------------

Could we reverse the dependency, and say that HttpServer requires a servlet container, and folks can pass in whatever they want?  I've been wanting to re-use the servlet container that AVRO uses for my own nefarious purposes (there's no reason to open up two ports if you've already got one open).  We should still have methods that work out of the box, as well.

> Allow pluggable ThreadPools in Java HttpServer
> ----------------------------------------------
>
>                 Key: AVRO-649
>                 URL: https://issues.apache.org/jira/browse/AVRO-649
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Stu Hood
>             Fix For: 1.4.1, 1.5.0
>
>         Attachments: 0001-Allow-an-alternate-ThreadPool-to-be-passed-to-the-Je.patch
>
>
> The easiest way to tune the threading implementation of an RPC server is to provide an alternate threadpool implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.