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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on GEODE-3993:
--------------------------------------------------------

Commit 95303fca05ec88a3d83f40dc21735d73f5e67717 in geode-native's branch refs/heads/develop from M. Oleske
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=95303fc ]

GEODE-3993: Remove poolName from  DataInput/Output (#261)

* Remove default parameter from DataInput/DataOutput ctors
* Removes default constructor from DataOutput.
* Replace poolname with pool.
* Replaced iPUF with ignorePdxUnreadFields.


> 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)