runtimeverification / runtimeverification/haskell-backend
(Proposal) kore-rpc - communicate via named pipe
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Currently, kore-rpc seems to communicate only via a TCP socket. One problem with this is that we cannot have two instances of kore-rpcrunning in parallel, unless we manually choose port numbers so they do not collide. With named pipe, we could simply create one in a temporary directory, and we would not have to care about whether another instance is running or not. I propose that we add a new parameter, --named-pipe <filename>, to kore-rpc, that could be used instead of --server-port.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the kore-rpc entry point and inspect how the existing --server-port option configures TCP communication. Determine how a --named-pipe alternative should integrate; done means two kore-rpc instances can communicate through separate named pipes without port collisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100