[ https://issues.apache.org/jira/browse/GEODE-10259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529683#comment-17529683 ]
ASF GitHub Bot commented on GEODE-10259: ---------------------------------------- pdxcodemonkey commented on code in PR #962: URL: https://github.com/apache/geode-native/pull/962#discussion_r861365008 ########## cppcache/src/ClientProxyMembershipID.cpp: ########## @@ -247,31 +243,26 @@ Serializable* ClientProxyMembershipID::readEssentialData(DataInput& input) { auto dsName = std::dynamic_pointer_cast<CacheableString>(input.readObject()); - initHostAddressVector(hostAddress, length); + initHostAddressVector(hostAddress.data(), length); - if (vmKind != ClientProxyMembershipID::LONER_DM_TYPE) { + if (vmKind != kVmKindLoaner) { // initialize the object with the values read and some dummy values - initObjectVars("", hostPort, "", std::chrono::seconds::zero(), DCPORT, 0, + initObjectVars("", hostPort, "", std::chrono::seconds::zero(), kDcPort, 0, vmKind, 0, dsName->value().c_str(), nullptr, vmViewId); } else { // initialize the object with the values read and some dummy values - initObjectVars("", hostPort, "", std::chrono::seconds::zero(), DCPORT, 0, + initObjectVars("", hostPort, "", std::chrono::seconds::zero(), kDcPort, 0, vmKind, 0, dsName->value().c_str(), uniqueTag->value().c_str(), vmViewId); } - - delete[] hostAddress; - readAdditionalData(input); - - return this; } void ClientProxyMembershipID::readAdditionalData(DataInput& input) { // Skip unused UUID (16) and weight (0); input.advanceCursor(17); } -void ClientProxyMembershipID::increaseSynchCounter() { ++synch_counter; } +void ClientProxyMembershipID::increaseSynchCounter() { ++synchCounter; } Review Comment: Seriously - what the heck does this thing do?????? It starts at 2, and `increaseSyncCounter` is called by the ThinClientPoolDM ctor, so is there only ever one of these(???). If so, it's yeah just always 3. It gets written into both clientId and memberId, but I also have no idea what, if any, information in those things is ever unpacked on the server side. > Update geode-native library protocol to 1.14 > -------------------------------------------- > > Key: GEODE-10259 > URL: https://issues.apache.org/jira/browse/GEODE-10259 > Project: Geode > Issue Type: Improvement > Reporter: Jacob Barrett > Priority: Major > Labels: pull-request-available > > The geode-native library still talks the Geode 1.0.0 protocol, update to at > 1.14. -- This message was sent by Atlassian Jira (v8.20.7#820007)