The custom RPC is not worth the bugs and copy/paste code. Switching to gRPC will make the build complex, but make new features simple.
Most of the code is RPC code, this will be removed and re-written as gRPC modules.
gRPC was chosen because it supports Python, Java and Javascript. This will make later development of UI easier. gRPC is also based on protobuf3 so we can output to JSON if we need to.
In this PR I will remove the tool_protocol on both python and java sides. I will also refactor the Ghidra tasks to start the inference side and manage it within Ghidra.
The custom RPC is not worth the bugs and copy/paste code. Switching to gRPC will make the build complex, but make new features simple.
Most of the code is RPC code, this will be removed and re-written as gRPC modules.
gRPC was chosen because it supports Python, Java and Javascript. This will make later development of UI easier. gRPC is also based on protobuf3 so we can output to JSON if we need to.
In this PR I will remove the
tool_protocolon both python and java sides. I will also refactor the Ghidra tasks to start the inference side and manage it within Ghidra.Closes #39