Comprehensive Refactoring of Protocol Handlers for Enhanced Performance and Readability

[merttozer]

This pull request introduces significant refactoring across three key components of the Hazelcast C++ client’s protocol handling: ClientMessageBuilder.h, list_cn_fixed_size_codec.h, and sql_page_codec.h. These changes leverage modern C++11 features to optimize performance, enhance readability, and improve error handling.

Detailed Changes:

1. ClientMessageBuilder.h:

• Redundant Checks: Simplified control flow by removing redundant checks, making the code easier to follow.
• Fragment Handling: Broke complex message fragmentation logic into smaller, more manageable functions.
• Duplication Reduction: Introduced helper functions to eliminate duplicated message completion checks.
• Naming Conventions: Improved variable and method names for greater clarity and maintainability.

2. list_cn_fixed_size_codec.h:

• Vector Initialization: Used std::fill to initialize vectors for the NULL_ONLY case, optimizing performance.
• Range-Based Loops: Implemented range-based for loops to simplify vector element modifications.

3. sql_page_codec.h:

• Vector Capacity Management: Utilized reserve to pre-allocate memory for vectors, reducing the need for reallocation.
• Range-Based Loops: Employed range-based for loops to streamline iteration over containers.
• Efficient Element Insertion: Used emplace_back to construct elements in place, enhancing performance.
• Explicit Null Handling: Added explicit handling for null values in vectors to maintain alignment and integrity.

Benefits:

• Performance Improvements: Reduced memory and processing overhead across multiple components.
• Increased Readability and Maintainability: Cleaner, more maintainable codebase due to modern C++ practices and clearer naming conventions.
• Enhanced Reliability and Safety: More robust error handling and safer memory management.

[devOpsHazelcast]

All committers have signed the CLA.

[devOpsHazelcast]

PR closed by Hazelcast automation as no activity (>3 months). Please reopen with comments, if necessary. Thank you for using Hazelcast and your valuable contributions