Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update logic in receiver to look for either transient headers or non-transient headers #6

Merged

Conversation

cwperks
Copy link

@cwperks cwperks commented Jul 5, 2023

This updates the logic in the SecurityRequestHandler to look to see whether transient (non-serialized) headers are present in the ThreadContext or if non-transient (serialized) headers are present. If transient headers are present, no deserialization needs to take place. If serialized headers are present than it will deserialized. The logic to determine whether to serialized headers or not is only placed in the sender. The headers will be serialized for requests to remote nodes, but no serialization should take place for requests on the local node.

@DarshitChanpura DarshitChanpura merged commit 691019b into DarshitChanpura:perf-bug-2724 Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants