Added timeouts for LispWorks. #4
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
This reverts commit 7212438.
Author
|
OK, here is a better version; I'm using the usocket LispWorks backend functions |
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.
I have added support for setting read and write timeouts on LispWorks. Testing has mainly consisted of successfully calling
(toot:start-server :port 8080 :handler (lambda (r) 'not-handled))as per the docs.I gather best practice is for the pull request to come from its own branch, but my Git-fu is pretty weak...
It's interesting that no other LispWorks user has found & tackled this issue in the last four years... :)
Cheers,
John :^P