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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace Daemon Communication Mechanism #1308
Replace Daemon Communication Mechanism #1308
Changes from 22 commits
478ecc4
8a3ba53
8792232
c12963b
995dc62
24c88b8
637aef9
71ea7f8
a7e7963
59a6077
9e46021
ada5600
fbe581a
9abd0f1
e1cf140
0c06766
a2d46df
f740a97
8a97ce4
e4a8676
f47c0de
539f7c0
cfbcc5d
eca24ae
15ba33e
60de50d
25b8e7e
905267a
3c8824d
4ef3962
f0aaad3
13f6250
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think our default values for named pipe or domain socket is less likely to conflict with something that the user is already using than the old port number. Another small benefit for the user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It definitely is. While it probably won't be used often, we've left the environment variable in place because it can be used to override where the socket file is being placed in a *nix environment. Ideally, the socket will be located at .zowe-daemon.sock in the user's home directory, but it can be moved in case the environment is strange and a problem occurs (i.e. a user logged into multiple workstations, all of which share the same user home directory on an NFS share.)