lobo/lambda-zig
1
1
Fork 1
Code Issues Pull Requests Actions Projects Releases Wiki Activity

calculate server requests based on lambda requests

Browse Source
This commit is contained in:
Emil Lerch 2023-08-02 13:55:14 -07:00
parent 180b0ec2ff
commit 194fdb8217
Signed by: lobo
GPG Key ID: A7B62D657EF764F8
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/lambda.zig
View File

@ -344,7 +344,11 @@ fn lambda_request(allocator: std.mem.Allocator, request: []const u8) ![]u8 {
// booleans to know when to shut down. This function is designed for a
// single request/response pair only
server_remaining_requests = 2; // Tell our server to run for just two requests
lambda_remaining_requests = 1; // in case anyone messed with this, we will make sure we start
server_remaining_requests = lambda_remaining_requests.? * 2; // Lambda functions
// fetch from the server,
// then post back. Always
// 2, no more, no less
server_response = request; // set our instructions to lambda, which in our
// physical model above, is the server response
defer server_response = "unset"; // set it back so we don't get confused later
@ -359,7 +363,6 @@ fn lambda_request(allocator: std.mem.Allocator, request: []const u8) ![]u8 {
defer server_thread.join(); // we'll be shutting everything down before we exit
// Now we need to start the lambda framework, following a siimilar pattern
lambda_remaining_requests = 1; // in case anyone messed with this, we will make sure we start
const lambda_thread = try test_run(allocator, handler); // We want our function under test to report leaks
lambda_thread.join();
return server_request_aka_lambda_response;