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

Joey McAllister updated GEODE-230:
----------------------------------
    Component/s: docs

> Remove deprecated AttributesFactory
> -----------------------------------
>
>                 Key: GEODE-230
>                 URL: https://issues.apache.org/jira/browse/GEODE-230
>             Project: Geode
>          Issue Type: Sub-task
>          Components: docs
>            Reporter: Darrel Schneider
>
> Should AttributesFactory be remove since it has been deprecated since 6.5.
> In that release we started telling customers to use Cache.createRegionFactory 
> or ClientCache.createClientRegionFactory.
> However here are a couple of reasons why we might not want to get rid of 
> AttributesFactory:
> - The corresponding PartitionAttributesFactory is not deprecated.
> - We have had customers request that it not be deprecated so that they have a 
> way to create a RegionAttributes on a client, send it to the server in a 
> function, and have the function create a region using the un-deprecated 
> Cache.createRegionFactory(RegionAttributes).
> We could argue that Cache.createRegionFactory(RegionAttributes) is not 
> deprecated so that given an existing region you could get its 
> RegionAttributes by calling Region.getAttributes. But it seems reasonable to 
> want to be able to create a RegionAttributes (and its nested 
> PartitionAttributes) without needing to create the region in the same jvm 
> that is creating the attributes.
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to