Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <32024986.154391288414582293.JavaMail.jira@thor>
Date: Sat, 30 Oct 2010 00:56:22 -0400 (EDT)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (POOL-178) Common interfaces and abstract classes
 for BOP and BKOP
In-Reply-To: <28407474.154371288414581945.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/POOL-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Gregory updated POOL-178:
------------------------------

    Attachment: POOL-178.diff

> Common interfaces and abstract classes for BOP and BKOP
> -------------------------------------------------------
>
>                 Key: POOL-178
>                 URL: https://issues.apache.org/jira/browse/POOL-178
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: Nightly Builds
>            Reporter: Gary Gregory
>             Fix For: 2.0
>
>         Attachments: POOL-178.diff
>
>
> I have created a patch that IMO should make it easier for us to further refactor code.
> In brief, OP/BOP and KOP/BKOP do not have a common parent interface/class. This patch remedies this by pulling up the close/clear/getNumActive/getNumIdle methods into a new interface and class.
> This seems not very controversial (to me at least), so I would like to commit it (unless riots spread from Paris to this list.)
> Thoughts?

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