You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Dan Smith <ds...@pivotal.io> on 2016/10/11 23:33:36 UTC
Deprecate DynamicRegionFactory
I'd like to reopen the discussion about deprecating
DynamicRegionFactory. This is some old crufty code I don't think we
want anyone to use. I see we had a ticket 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 from the client. Personally I'd recommend that over
DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
and implement GEODE-215 later?
-Dan
Re: Deprecate DynamicRegionFactory
Posted by Bruce Schuchardt <bs...@pivotal.io>.
+1
Le 10/12/2016 � 6:36 AM, Jens Deppe a �crit :
> +1 to remove it
>
> On Tue, Oct 11, 2016 at 9:33 PM, John Blum <jb...@pivotal.io> wrote:
>
>> +1 - forget deprecated; delete it.
>>
>> On Tue, Oct 11, 2016 at 8:22 PM, Udo Kohlmeyer <uk...@pivotal.io>
>> wrote:
>>
>>> +1 - I see no real benefit for this.
>>>
>>>
>>>
>>> On 12/10/16 1:10 pm, William Markito wrote:
>>>
>>>> +1 - We always discouraged people using dynamic regions
>>>>
>>>> On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <ds...@pivotal.io> wrote:
>>>>
>>>> I'd like to reopen the discussion about deprecating
>>>>> DynamicRegionFactory. This is some old crufty code I don't think we
>>>>> want anyone to use. I see we had a ticket 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 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)
>>
Re: Deprecate DynamicRegionFactory
Posted by Jens Deppe <jd...@pivotal.io>.
+1 to remove it
On Tue, Oct 11, 2016 at 9:33 PM, John Blum <jb...@pivotal.io> wrote:
> +1 - forget deprecated; delete it.
>
> On Tue, Oct 11, 2016 at 8:22 PM, Udo Kohlmeyer <uk...@pivotal.io>
> wrote:
>
> > +1 - I see no real benefit for this.
> >
> >
> >
> > On 12/10/16 1:10 pm, William Markito wrote:
> >
> >> +1 - We always discouraged people using dynamic regions
> >>
> >> On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <ds...@pivotal.io> wrote:
> >>
> >> I'd like to reopen the discussion about deprecating
> >>> DynamicRegionFactory. This is some old crufty code I don't think we
> >>> want anyone to use. I see we had a ticket 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 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)
>
Re: Deprecate DynamicRegionFactory
Posted by John Blum <jb...@pivotal.io>.
+1 - forget deprecated; delete it.
On Tue, Oct 11, 2016 at 8:22 PM, Udo Kohlmeyer <uk...@pivotal.io>
wrote:
> +1 - I see no real benefit for this.
>
>
>
> On 12/10/16 1:10 pm, William Markito wrote:
>
>> +1 - We always discouraged people using dynamic regions
>>
>> On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <ds...@pivotal.io> wrote:
>>
>> I'd like to reopen the discussion about deprecating
>>> DynamicRegionFactory. This is some old crufty code I don't think we
>>> want anyone to use. I see we had a ticket 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 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)
Re: Deprecate DynamicRegionFactory
Posted by Udo Kohlmeyer <uk...@pivotal.io>.
+1 - I see no real benefit for this.
On 12/10/16 1:10 pm, William Markito wrote:
> +1 - We always discouraged people using dynamic regions
>
> On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <ds...@pivotal.io> wrote:
>
>> I'd like to reopen the discussion about deprecating
>> DynamicRegionFactory. This is some old crufty code I don't think we
>> want anyone to use. I see we had a ticket 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 from the client. Personally I'd recommend that over
>> DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
>> and implement GEODE-215 later?
>>
>> -Dan
>>
>
>
Re: Deprecate DynamicRegionFactory
Posted by Jinmei Liao <ji...@pivotal.io>.
+1 drop it if we don't want people to use it.
On Tue, Oct 11, 2016 at 8:15 PM, Kirk Lund <kl...@apache.org> wrote:
> +1 drop it as a bug with no need for replacement (or in favor of using a
> function)
>
> On Tuesday, October 11, 2016, William Markito <wm...@pivotal.io> wrote:
>
> > +1 - We always discouraged people using dynamic regions
> >
> > On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <dsmith@pivotal.io
> > <javascript:;>> wrote:
> >
> > > I'd like to reopen the discussion about deprecating
> > > DynamicRegionFactory. This is some old crufty code I don't think we
> > > want anyone to use. I see we had a ticket 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 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
Re: Deprecate DynamicRegionFactory
Posted by Kirk Lund <kl...@apache.org>.
+1 drop it as a bug with no need for replacement (or in favor of using a
function)
On Tuesday, October 11, 2016, William Markito <wm...@pivotal.io> wrote:
> +1 - We always discouraged people using dynamic regions
>
> On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <dsmith@pivotal.io
> <javascript:;>> wrote:
>
> > I'd like to reopen the discussion about deprecating
> > DynamicRegionFactory. This is some old crufty code I don't think we
> > want anyone to use. I see we had a ticket 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 from the client. Personally I'd recommend that over
> > DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
> > and implement GEODE-215 later?
> >
> > -Dan
> >
>
>
>
> --
>
> ~/William
>
Re: Deprecate DynamicRegionFactory
Posted by William Markito <wm...@pivotal.io>.
+1 - We always discouraged people using dynamic regions
On Tue, Oct 11, 2016 at 4:33 PM, Dan Smith <ds...@pivotal.io> wrote:
> I'd like to reopen the discussion about deprecating
> DynamicRegionFactory. This is some old crufty code I don't think we
> want anyone to use. I see we had a ticket 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 from the client. Personally I'd recommend that over
> DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now
> and implement GEODE-215 later?
>
> -Dan
>
--
~/William