geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob S. Barrett (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-3993) Re-evaluate the Cache.createDataInput/Output API
Date Fri, 17 Nov 2017 18:22:00 GMT
Jacob S. Barrett created GEODE-3993:
---------------------------------------

             Summary: 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


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
(v6.4.14#64029)

Mime
View raw message