Mailing-List: contact dev-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dsetrakyan@gridgain.com
 designates 209.85.214.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGt6o8=HxNJpPUCPGJ+9hgTCP9qCPZORRXL2BsGmn7dOir8Rfg@mail.gmail.com>
References: 
 <CAGt6o8=HxNJpPUCPGJ+9hgTCP9qCPZORRXL2BsGmn7dOir8Rfg@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@gridgain.com>
Date: Fri, 3 Apr 2015 07:07:30 -0700
Message-ID: 
 <CA+0=VoWmgJp3DwDcuMgSGFanux5tix0Be9QvFHCpO3q39CeFwA@mail.gmail.com>
Subject: Re: Ignite component class names.
To: "dev@ignite.incubator.apache.org" <dev@ignite.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a11c1f4027dc6ae0512d27ac4

--001a11c1f4027dc6ae0512d27ac4
Content-Type: text/plain; charset=UTF-8

Agree.

On Fri, Apr 3, 2015 at 5:24 AM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Hi,
>
> We removed "Grid" prefix from all public API in Ignite. However, we still
> have odd namings in internal classes which can be used by plugin
> developers. E.g.:
>
> DR:
> GridCacheDrManager - DR manager interaface;
> GridOsCacheDrManager - Ignite implementation of DR manager;
>
> Cache objects:
> IgniteCacheObjectProcessor - interface;
> IgniteCacheObjectProcessorImpl - implementation.
>
> It seems to me that we should ensure that all components which can
> potentially be exposed to plugin developers should have consistent namings
> as well. E.g.:
> GridCacheDrManager -> CacheDrManager
> GridOsCacheDrManager -> IgniteCacheDrManager (other implementors could
> follow [Vendor]CacheDrManager pattern).
>
> If we do not do that now, we will have to preserve these inconsistent names
> because their refactoring will brake third-party plugins.
>
> Thoughts?
>

--001a11c1f4027dc6ae0512d27ac4--