Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Restoration of TCP conn functionality #111

Closed
reube opened this issue Nov 6, 2017 · 3 comments
Closed

Restoration of TCP conn functionality #111

reube opened this issue Nov 6, 2017 · 3 comments

Comments

@reube
Copy link
Contributor

reube commented Nov 6, 2017 •
edited

Please see pull request: #110

thx Andrew
@jooste
Copy link
Member

jooste commented Nov 6, 2017

Hi Andrew,

Can you explain a bit more why you need reply's to every tcp command? Is this an implementation thing on the client side, or a timeout issue?

Thanks!

@reube
Copy link
Contributor Author

reube commented Nov 6, 2017 •
edited

Hi Joost. Its helpful to have explicit feedback as a (tcp) client for any of the actions, including those that are 'puts/sets' rather than 'gets'. Ie, for writing control scripts against bluesky using the tcp interface.
Thx A

@reube
Copy link
Contributor Author

reube commented Nov 14, 2017

merged 8874763

@reube reube closed this as completed Nov 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reube @jooste