geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Stolz <mst...@pivotal.io>
Subject Re: Use InternalCache instead of GemFireCacheImpl
Date Mon, 15 May 2017 23:40:46 GMT
While we are going down this path, could read-serialized be a Region
property?

--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771

On May 15, 2017 7:22 PM, "Jacob Barrett" <jbarrett@pivotal.io> wrote:

> This is an awesome step forward!
>
> We are getting close to committing similar refactoring on the C++ client to
> move away from globals too.
>
> Death to globals!
>
> -Jake
>
> On Mon, May 15, 2017 at 1:03 PM Kirk Lund <klund@apache.org> wrote:
>
> > I just merged in a big refactoring which changes classes that were using
> > GemFireCacheImpl to using InternalCache.
> >
> > InternalCache is an interface representing the internal view of Cache
> which
> > exposes all the operations that aren't exposed in the User API of Cache
> or
> > GemFireCache. InternalCache and GemFireCacheImpl are still too big and
> need
> > to be broken out but this is one step in refactoring.
> >
> > If you need to create or change a class to use GemFireCacheImpl, please
> > make that class depend on InternalCache instead. Also, please pass the
> > InternalCache instance to the constructor instead of reaching out from
> the
> > class to call GemFireCacheImpl.getInstance or
> CacheFactory.getAnyInstance.
> > This will reduce the number of classes we need to change in further
> > refactoring to reduce the use of these singleton accessors.
> >
> > If you encounter any merge conflicts caused by my commit, please let me
> > know and I'll do what I can to help.
> >
> > Thanks,
> > Kirk
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message