-
Notifications
You must be signed in to change notification settings - Fork 506
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
Additional client information websocket #393
Additional client information websocket #393
Conversation
Looks good. Thanks. |
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.
Thanks. Just small nits
def remove_client(self, client_id, ip_address): | ||
with self._lock: | ||
self._clients.pop(client_id, None) | ||
self.__publish() |
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.
Small NITS: wrong indentation.
|
||
def add_client(self, client_id, ip_address): | ||
with self._lock: | ||
client = ConnectedClient() |
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.
here too
This PR has quite some commits now. I can rebase and squash my commits if that desired. |
Note that this PR introduced a new dependency on rosbridge_server. So, we need to release with minor patch bump for the next release. |
I would like to prevent certain IP addresses from connecting to rosbridge websocket server. |
@ramezanifar system firewall features are good for that, if you are using Ubuntu look at |
Latches a list of all connected clients, where each client is described by
This only works for the websocket server for now. Let me know if this is something useful. If so, then I will look into adding this functionality also to the other backends.