Remove legacy gherkin references
ober
01d2fa8c38ad79edc81868a35ec42c9383ad4f7b
--- a/chez-https.md +++ b/chez-https.md @@ -6,7 +6,7 @@ Provide a complete HTTP/1.1 client for Chez Scheme that works over TLS (HTTPS). ## Why This Is Needed -This project (`gherkin-kunabi`) currently shells out to `curl` for every HTTP request. With 27,000+ S3 objects to download, that spawns 27,000+ subprocesses, causing catastrophic memory leaks. This library replaces all of that with native in-process HTTPS. +The original client currently shells out to `curl` for every HTTP request. With 27,000+ S3 objects to download, that spawns 27,000+ subprocesses, causing catastrophic memory leaks. This library replaces all of that with native in-process HTTPS. ## Dependencies @@ -258,11 +258,11 @@ S3 may redirect if the bucket region doesn't match. For now, raise an error with (assert (= (length flat) 2)))) ``` -## Integration into gherkin-kunabi +## Integration Once `chez-ssl` and `chez-https` exist, the integration is: -1. Replace `gherkin-aws/src/compat/request.sls` with the new `(compat request)` that imports `(chez-ssl)` and does native HTTPS +1. Replace the existing request compatibility module with the new `(compat request)` that imports `(chez-ssl)` and does native HTTPS 2. Add `(ssl-init!)` call in `kunabi-main.sls` at startup 3. Add `chez_ssl_shim.o` to the binary link step in `build-binary.ss` 4. Add `-lssl -lcrypto` to the linker flags (already linking other system libs)