Redis and Flatbuffers Integration for Event Handling #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Integrated Redis for event handling and added relevant configurations in `ServerState` and `ServerSettings`. Updated README with installation and configuration instructions for Redis and improved some log messages.
Integrated Flatbuffers for event serialization and deserialization in the application. Added new schemas module and relevant dependencies, along with updates to the README for Flatbuffers installation and usage.
Reformatted the FlatBuffers schema for better readability and consistency. Adjusted indentation and spacing to align with recommended coding standards.
Reformatted async function calls in `main.rs` for better readability and consistency. Standardized indentation in `schemas/event_generated.rs` for better code quality and maintainability.
Refactor event handling to support multiple event types, including UserEvent and CacheEvent. Extend the event schema with additional action types and a new CacheEvent structure to better manage event data.
Convert `event_data` to a byte vector and improve logging for event retrieval and caching process. This ensures more robust type handling for Redis data and adds detailed information about target payloads and their sizes.
Converted Redis commands to use explicit type parameters for better readability and type safety. This change ensures the correct types are enforced at compile-time, reducing runtime errors and improving code clarity.
Break long Redis `set_ex` call across multiple lines for readability in `src/bin/main.rs`. Introduce 'unused' enum variants and update maximum values to reflect the new actions and statuses in `src/bin/schemas/event_generated.rs`. This change improves the organization and handling of enums by marking unused slots explicitly.
Simplify the TLS acceptor setup by introducing custom options, such as setting the minimum TLS version to 1.2. Additionally, restore the original import order for consistency and add validation to check for zero-sized data from Redis.
Refactor the TLS setup to streamline the function call and simplify the Redis cache logic by combining nested conditions. Clean up redundant lifetime annotations in `event_generated.rs` to improve code readability.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Redis Integration:
• Integrated Redis as a backend for event handling to improve performance and scalability.
• Updated ServerState and ServerSettings with Redis configurations.
• Enhanced logging for better insight into event handling processes.
• Updated the README with Redis installation and configuration instructions.
Flatbuffers Integration:
• Integrated Flatbuffers for efficient event serialization and deserialization.
• Added a new schemas module for Flatbuffers schema files.
• Updated dependencies to include Flatbuffers.
• Updated the README with steps for Flatbuffers installation and usage.
Other improvements include enhanced log messages and updates to documentation.