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

Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/04/20 19:57:21 UTC

[jira] [Closed] (GEODE-3993) Re-evaluate the Cache.createDataInput/Output API

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

Anthony Baker closed GEODE-3993.
--------------------------------

> Re-evaluate the Cache.createDataInput/Output API
> ------------------------------------------------
>
>                 Key: GEODE-3993
>                 URL: https://issues.apache.org/jira/browse/GEODE-3993
>             Project: Geode
>          Issue Type: Task
>          Components: native client
>            Reporter: Jacob S. Barrett
>            Assignee: Blake Bender
>            Priority: Major
>
> Having the factory on Cache is convenient for end users but produces DataInput/Output objects that are not usable for internal use because it relies on access to the Pool. If a User's use of the DataInput/Output also needs Pool then it will be broken.  Internally we turn around and call an internal API to add the Pool to the DataInput/Output. This all seems really dirty, can we do better?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)