geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Stolz <mst...@pivotal.io>
Subject Re: New APIs, read-serialized and CacheListeners, PostProcessor etc
Date Tue, 27 Mar 2018 05:05:50 GMT
in addition to not breaking existing callbacks, new getvalue mechanisms
should be created that support either getting the serialized or
deserialized value on the call itself rather than at the thread level or
the entire cache level.

--
Mike Stolz
Principal Engineer, GemFire Product Lead
Mobile: +1-631-835-4771
Download the new GemFire book here.
<https://content.pivotal.io/ebooks/scaling-data-services-with-pivotal-gemfire>

On Tue, Mar 27, 2018 at 3:06 AM, Galen O'Sullivan <gosullivan@pivotal.io>
wrote:

> Hi all,
>
> We're working on a new protocol for Geode, which means wrapping Geode APIs
> and exposing them via the new protocol. For performance and to avoid
> class/serialization logic, we want to get these objects in serialized form.
> This means calling cache.setReadSerializedForCurrentThread(true) while
> we're operating.
>
> However, what side effects might this have on CacheListeners or other
> user-defined callbacks? Looking at the API for CacheListener, it's not
> clear whether EntryEvent.getOldValue respects the value of
> pdx-read-serialized or whether it always deserialized (since there is an
> associated getSerializedOldValue method here). There is also PostProcessor
> and may be other APIs that will be affected as well.
>
> So, how do we make sure we don't break callbacks? Is there an API I don't
> know about for getting entries in PDX serialized format (or whatever format
> they're currently in in the region)?
>
> Thanks,
> Galen
>

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