Skip to content

Conversation

obelisk
Copy link
Collaborator

@obelisk obelisk commented Nov 11, 2019

Closes #91

If you’re already connected we don’t send another query all the way down to remote host before allowing you to interact with it again, instead just checking the backend is responding before immediately switching state.
PNG image

@terracatta

@obelisk obelisk added the UX For things relating to the experience of someone using goquery label Nov 11, 2019
@obelisk obelisk self-assigned this Nov 11, 2019
if newHost.UUID == host.UUID {
currentHostIndex = i
return nil
return fmt.Errorf("Active Host Switched")
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of misusing how errors are set up here, I would suggest that the caller does print after this Register call, or the line above the return here does a print

@obelisk obelisk added this to the 2.0 Release milestone Dec 14, 2019
@AbGuthrie AbGuthrie removed this from the 2.0 Release milestone Jan 17, 2020
@obelisk obelisk added this to the 2.1.0 Release milestone Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

UX For things relating to the experience of someone using goquery

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Don't Revalidate Host on Switch

2 participants