Persistent Connections #15
Open
Conversation
This file contains hidden or 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
The request record now contains the pid of the receive_term process #request.con_pid which allows to report back once the processing is done. After the receive_term function kicked the queue it waits for this signal (#request.con_pid ! done) that the request has been executed and calls itself with an extra receive-timeout parameter (e.g. 10seconds) preventing socket starvation. This is implemented for call/cast in external and native handlers.
This should be configurable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Basic implementation for persistent connections
The request record now contains the pid of the receive_term process
#request.con_pidwhich allows to report back once the processing is done. After thereceive_termfunction kicked the queue it waits for this signal (#request.con_pid ! done) that the request has been executed and calls itself with an extra receive-timeout parameter (e.g. 10 seconds) preventing socket starvation. From here either a new request is received over the same connection or the receive times out which closes the socket.This is implemented for call/cast in external and native handlers.