Rename IgniteBinary to IgniteBinaries?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Rename IgniteBinary to IgniteBinaries?

Vladimir Ozerov
Folks,

One more minor question about API. We use plural form when possbile in
top-level API. E.g.:

   - IgniteTransactions transactions()
   - IgniteEvents events()

Shouldn't we rename our API to IgniteBinar*ies* binar*ies*()?

Vladimir.
Reply | Threaded
Open this post in threaded view
|

Re: Rename IgniteBinary to IgniteBinaries?

dsetrakyan
I prefer IgniteBinary. The plural form sounds like a release archive.

D.

On Thu, Nov 26, 2015 at 12:20 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Folks,
>
> One more minor question about API. We use plural form when possbile in
> top-level API. E.g.:
>
>    - IgniteTransactions transactions()
>    - IgniteEvents events()
>
> Shouldn't we rename our API to IgniteBinar*ies* binar*ies*()?
>
> Vladimir.
>
Reply | Threaded
Open this post in threaded view
|

Re: Rename IgniteBinary to IgniteBinaries?

Vladimir Ershov
Imho, *IgniteBinaryProto *is also an option.

Vladimir.


On Thu, Nov 26, 2015 at 12:51 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> I prefer IgniteBinary. The plural form sounds like a release archive.
>
> D.
>
> On Thu, Nov 26, 2015 at 12:20 PM, Vladimir Ozerov <[hidden email]>
> wrote:
>
> > Folks,
> >
> > One more minor question about API. We use plural form when possbile in
> > top-level API. E.g.:
> >
> >    - IgniteTransactions transactions()
> >    - IgniteEvents events()
> >
> > Shouldn't we rename our API to IgniteBinar*ies* binar*ies*()?
> >
> > Vladimir.
> >
>