Perhaps for others on this list that aren’t familiar with the context you could fill in the blanks.
It is assumed you are asking about the “feature” where PDX metadata is propagated from one connection pool to another in an attempt to support multiple distributed systems in the same client. While the short answer is yes, Geode Native (GN) goes further in not requiring one to share clients across multiple distributed systems. You can create multiple independent caches in the same process space with GN. Each of these instances can be connected to independent distributed systems. The need to copy PDX metadata goes away. The need to create multiple pools to different systems goes away. All the pain and issues of supporting this “feature” just goes away. So if there is someone out there wanting to do what was done before I would strongly encourage to not and instead use independent caches. -Jake > On Mar 26, 2019, at 9:50 AM, Michael Stolz <mst...@pivotal.io> wrote: > > Thanks. I'm happy to hear that. > > > -- > Mike Stolz > Principal Engineer, GemFire Product Lead > Mobile: +1-631-835-4771 > > On Tue, Mar 26, 2019, 12:46 PM Blake Bender <bben...@pivotal.io> wrote: > >> Okay, after a conversation here at the office with folks who know, I can >> confirm the answer is "yes," NC has code to copy PDX types in the manner >> you're asking after. >> >> Thanks, >> >> Blake >> >> >> On Tue, Mar 26, 2019 at 8:43 AM Blake Bender <bben...@pivotal.io> wrote: >> >>> Hi Mike, >>> >>> I'm not 100% certain what you're referring to, but... PdxSerializable in >>> NC has toData and fromData methods that allow you to copy objects via >>> serialization. That what you're looking for? >>> >>> Thanks, >>> >>> Blake >>> >>> >>> On Mon, Mar 25, 2019 at 12:53 PM Michael Stolz <mst...@pivotal.io> >> wrote: >>> >>>> Does this functionality exist in the Native Client as well as the Java >>>> Client? >>>> >>>> -- >>>> Mike Stolz >>>> Principal Engineer, GemFire Product Lead >>>> Mobile: +1-631-835-4771 >>>> >>> >>
