You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IPC service and headless Client are really two different things that share a lot of code down in the shared connlib crates.
If a user is setting up the headless Client, they aren't going to want the IPC service. If they're setting up the GUI, they probably won't need the headless Client. If they do need both, they should be separate files to avoid package conflicts. If they're separate files, they might as well be separate binaries and separate packages.
While doing this, also make the function names better. Stuff like run_ipc_service and ipc_listen is not intuitive at all. If there's enough layers maybe they should just get numbers.
The text was updated successfully, but these errors were encountered:
Closes#4907
They're still accepted, but the binary entirely determines the behavior.
This makes the code for CLI parsing and token handling simpler with
fewer branches, so it's easier to be sure it's correct.
Replaces #4942 which isn't doing what I intended anymore.
The IPC service and headless Client are really two different things that share a lot of code down in the shared connlib crates.
If a user is setting up the headless Client, they aren't going to want the IPC service. If they're setting up the GUI, they probably won't need the headless Client. If they do need both, they should be separate files to avoid package conflicts. If they're separate files, they might as well be separate binaries and separate packages.
This will simplify some of the code for #4903 too
While doing this, also make the function names better. Stuff like
run_ipc_service
andipc_listen
is not intuitive at all. If there's enough layers maybe they should just get numbers.The text was updated successfully, but these errors were encountered: