[
https://issues.apache.org/jira/browse/GEODE-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284477#comment-16284477
]
ASF subversion and git services commented on GEODE-3645:
--------------------------------------------------------
Commit b19a2962428c723fbe4a290f847d2185106d01a5 in geode-native's branch
refs/heads/develop from [~dkimura]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=b19a296 ]
GEODE-3645: Fix SEGV in cache destructor
> Update API CacheFactory::create to return cache object
> ------------------------------------------------------
>
> Key: GEODE-3645
> URL: https://issues.apache.org/jira/browse/GEODE-3645
> Project: Geode
> Issue Type: New Feature
> Components: native client
> Reporter: David Kimura
>
> As an application developer I want to control the stack vs heap allocation of
> my cache object. If we change CacheFactory::create to return a cache object
> then the application user can pick an allocation scheme. This also allows
> application developers to bypass smart pointer complexity until the developer
> deems them necessary.
> Example:
> {noformat}
> auto cache = CacheFactory::createFactory().create();
> auto cacheptr =
> std::make_shared<Cache>(CacheFactory::createFactory().create());
> {noformat}
> Difficulty of implementation is due to Cache/CacheImpl circular dependency.
> Here are a few examples of various approaches to consider:
> https://gist.github.com/pivotal-jbarrett/52ba9ec5de0b494368d1c5282ef188ef
> https://gist.github.com/pivotal-jbarrett/c48ffff3f7f41b187f0ed8c80108aa6a
> Here are the related email threads of interest:
> http://markmail.org/message/in5e337npq5euslh
> http://markmail.org/message/lp2rx2rtyblg72fv
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
