nt. Personally I'd recommend that over
DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
and implement GEODE-215 later?
-Dan
--
-John
503-504-8657
john.blum10101 (skype)
lternative API to create regions from the client (GEODE-215).
> >>>
> >>> The thing is, there is a pretty easy workaround to use functions to
> >>> create regions from the client. Personally I'd recommend that over
> >>> DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
> >>> and implement GEODE-215 later?
> >>>
> >>> -Dan
> >>>
> >>>
> >>
> >>
> >
>
>
> --
> -John
> 503-504-8657
> john.blum10101 (skype)
>
t to deprecated it
>>> (GEODE-388), but we chose not to do it because we don't have an
>>> alternative API to create regions from the client (GEODE-215).
>>>
>>> The thing is, there is a pretty easy workaround to use functions to
>>> create regions f
create regions from the client. Personally I'd recommend that over
DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
and implement GEODE-215 later?
-Dan
DE-215).
> > >
> > > The thing is, there is a pretty easy workaround to use functions to
> > > create regions from the client. Personally I'd recommend that over
> > > DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
> > > and implement GEODE-215 later?
> > >
> > > -Dan
> > >
> >
> >
> >
> > --
> >
> > ~/William
> >
>
--
Cheers
Jinmei
onally I'd recommend that over
> DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
> and implement GEODE-215 later?
>
> -Dan
>
--
~/William
(GEODE-215).
The thing is, there is a pretty easy workaround to use functions to
create regions from the client. Personally I'd recommend that over
DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
and implement GEODE-215 later?
-Dan