-
Notifications
You must be signed in to change notification settings - Fork 20
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
Check that a chromote connection is alive #136
Changes from all commits
acc89fc
e2a7a95
2fd9552
6e0cf52
f5a7850
c029dce
6df996a
add90d3
e8656a5
b1cffad
2f39a89
ef173a6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
What do you think about
target_is_alive
? (I'm asking honestly, not suggesting that it should or should not be that name.) I ask because it might help conceptually separate the twoalive
names. Also the target exists independently of any connection to it, sort of like how the Chrome process exists independently of a connection to it, and in that case we call it alive.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 don't mind changing the name, but calling it
alive
does introduce another inconsistency —Chromote$is_alive()
is always accurate because we have a connection to the process that we can check; but there's currently no analog for the target. I could add anis_alive()
method that checks if the target ID is found in the chromote instance, but I'm not sure if that's worth it (plus calling that repeatedly might be expensive).So while I agree that "active" isn't the best name, and has some potential for confusion, I think changing it to "alive" is a net neutral because it just introduces a different source confusion.
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.
OK, let's keep it as "active" then.