The Wayback Machine - https://web.archive.org/web/20210726103332/https://github.com/microsoft/tensorwatch/issues/30
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.

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

How to use Watcher / WatcherClient over tcp/ip network? (ex. cloud - local) #30

Open
orihime-kitajima opened this issue Jul 3, 2019 · 2 comments

Comments

@orihime-kitajima
Copy link

@orihime-kitajima orihime-kitajima commented Jul 3, 2019

How to use Watcher / WatcherClient over tcp/ip network?

Watcher seems to ZMQ server, and WatcherClient is ZMQ Client, but there is no API/Interface to config server IP address.
Do I need to implement a class that inherits from WatcherClient?

@sytelus
Copy link
Contributor

@sytelus sytelus commented Jul 10, 2019

We are currently exposing port in constructor but you are absolutely correct that we need to have IP address as well. This is almost trivial change and we will add very soon!

@taehyunoh
Copy link

@taehyunoh taehyunoh commented Jul 18, 2019

I’m just curious whether ssh port tunneling from a remote server to the local host would work in this case??
This would be a workaround at this moment until TCP/IP support is made, but not sure whether ZMQ is compatible with port forwarding. Any idea?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants