cov...@amdocs.com> wrote:
> Raising this question again.
>
> Daniel
>
> From: Daniel Farcovich
> Sent: Wednesday, July 05, 2017 1:26 PM
> To: 'dev@geode.apache.org' <dev@geode.apache.org>
> Subject: getSizeInBytes() return type
>
>
> Hi,
> We implement getSiz
> >
> > From: Daniel Farcovich
> > Sent: Wednesday, July 05, 2017 1:26 PM
> > To: 'dev@geode.apache.org' <dev@geode.apache.org>
> > Subject: getSizeInBytes() return type
> >
> >
> > Hi,
> > We implement getSizeInBytes() in from Sizeable i
<
daniel.farcov...@amdocs.com> wrote:
> Raising this question again.
>
> Daniel
>
> From: Daniel Farcovich
> Sent: Wednesday, July 05, 2017 1:26 PM
> To: 'dev@geode.apache.org' <dev@geode.apache.org>
> Subject: getSizeInBytes() return type
>
>
> Hi,
>
Raising this question again.
Daniel
From: Daniel Farcovich
Sent: Wednesday, July 05, 2017 1:26 PM
To: 'dev@geode.apache.org' <dev@geode.apache.org>
Subject: getSizeInBytes() return type
Hi,
We implement getSizeInBytes() in from Sizeable interface.
We have objects with size bigger than
Hi,
We implement getSizeInBytes() in from Sizeable interface.
We have objects with size bigger than MAXINT, bigger than 2GB.
What is the impact of refactoring the code to return long instead of int? I
mean except the technical aspect of changing the return types of the calling
functions etc.