Blake Bender created GEODE-7584:
-----------------------------------

             Summary: Refactor PDX handling in ThinClientPoolDM
                 Key: GEODE-7584
                 URL: https://issues.apache.org/jira/browse/GEODE-7584
             Project: Geode
          Issue Type: Improvement
          Components: native client
            Reporter: Blake Bender


As a native client developer, I would very much like to fully understand what's 
going on in the PDX serialization/deserialization code.  Unfortunately, much of 
this code is opaque and full of side-effect.  For instance, 
ThinClientPoolDM::GetPDXIdForType first gets the type, which registers the type 
on the specific server the pool is talking to, then it broadcasts the type 
information to any/all other existing pools in the client.  Cleaning up some of 
this stuff so you can see the discrete steps the code is executing will go a 
long way towards making it readable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to