Lambda wrapper - start TLS connection on init & RequestClientKeptAlive #328
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
16pierre
force-pushed
the
quentin.pierre/aws-lambda-decorator
branch
2 times, most recently
from
a60fb93
to
ce25a4a
Compare
16pierre
force-pushed
the
quentin.pierre/aws-lambda-decorator
branch
from
ce25a4a
to
637d5a4
Compare
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.
Adds a new HTTPClient:
RequestClientKeptAlive. It keeps therequestssession alive.Adds a no-op POST request on lambda_wrapper initialization: this initializes
RequestClientKeptAlive's connection to our endpoint at the beginning of the lambda executions instead of at the end: this enables to us to use an async initialization.Note: the connection to our endpoint is kept alive across multiple invocations of the same lambda thanks to AWS's context reuse.