[feature] signal on a semaphore when the proxy-server is initialized #2
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.
This change is blocked by GaloisInc/http-server#9
If one wants to run the proxy within a larger program in its own thread, it is advantageous to know when the proxy has finished initializing.
proxyMain
toproxyMain_
and changed it to accept an additionalMVar ()
argument. It signals (non blocking) on that semaphore just before waiting on the socket for connections (pending [feature] signal on a semaphore when the server is initialized GaloisInc/http-server#9).proxyMain
which does exactly what the old one did, but usesproxyMain_
.stack.yaml
file for users of stack and included its work dir to the.gitignore
file.Changes to the API dictate a minor-version bump (adding a new function).