You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Dan Smith (Jira)" <ji...@apache.org> on 2019/12/06 00:30:00 UTC

[jira] [Commented] (GEODE-7555) Move API for creating and finding Pools to ClientCache

    [ https://issues.apache.org/jira/browse/GEODE-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989276#comment-16989276 ] 

Dan Smith commented on GEODE-7555:
----------------------------------

Wiki proposal - https://cwiki.apache.org/confluence/display/GEODE/Replace+singleton+PoolManager+with+ClientCache+scoped+service

> Move API for creating and finding Pools to ClientCache
> ------------------------------------------------------
>
>                 Key: GEODE-7555
>                 URL: https://issues.apache.org/jira/browse/GEODE-7555
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Dan Smith
>            Priority: Major
>
> Currently, users must use the static PoolManager class to create and lookup Pools on the client side. This is problematic for several reasons:
> 1. PoolManager is hard to mock because it consists of static methods
> 2. Being a static singleton with state, PoolManager locks the client into only having one PoolManager and associated ClientCache.
> 3. The lifecycle of Pools in the PoolManager is strange, they can be created before or after the ClientCache, but they are destroyed when the ClientCache is destroyed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)