-
Notifications
You must be signed in to change notification settings - Fork 0
Revision #1
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
Revision #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great progress!
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
The proposed design of passing a `LambdaResponseWriter` as an argument to the `handle` function of objects conforming to | ||
`StreamingLambdaHandler` already allows for background tasks to be run _after_ the response has been returned. This is | ||
because the `handle(...)` function is free to implement any background task that needs to be run after calling the | ||
`LambdaResponseWriter.finish()` function (which sends the computed result to the AWS Lambda response endpoint). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also users are able to spawn async work in structured way. They can start TaskGroups or schedule work using async let (both of which are totally structured).
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
Sources/AWSLambdaRuntimeCore/Documentation.docc/Proposals/0001-v2-api.md
Outdated
Show resolved
Hide resolved
/// If no response or error is written to the `responseWriter` it will | ||
/// report an error to the invoker. | ||
/// - context: The LambdaContext containing the invocation's metadata | ||
mutating func handle(_ event: ByteBuffer, responseWriter: consuming some LambdaResponseWriter, context: LambdaContext) async | ||
/// - Throws |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/// - Throws | |
/// - Throws: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.