Define the planner interface and transition the daemon to be a child process #75
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.
Part of #62 and #63.
Previously we needed to launch the daemon process independently. For simplicity for now, we will have the server automatically launch it as a subprocess (thus we assume that the daemon process runs on the same physical machine as the server process).
Later on we can decouple the daemon and have it communicate with the main server process over RPC instead, but this is engineering work that is not currently necessary.