Feature Request
On Windows, the GUI talks to the service via TCP IPC. Not only is this overkill for IPC, but there are some limitations; one example is that Windows tends to hang on a socket resource if not properly released by the process, requiring a reboot for the underlying socket resource to be released (this doesn't tend to affect the user but is horrible for development).
Simplify the IPC communication by using files and local pipes/file sockets instead, which would reduce the maintenance burden. Logs can make their way to the GUI through log files.
Related:
Feature Request
On Windows, the GUI talks to the service via TCP IPC. Not only is this overkill for IPC, but there are some limitations; one example is that Windows tends to hang on a socket resource if not properly released by the process, requiring a reboot for the underlying socket resource to be released (this doesn't tend to affect the user but is horrible for development).
Simplify the IPC communication by using files and local pipes/file sockets instead, which would reduce the maintenance burden. Logs can make their way to the GUI through log files.
Related: