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

We need a --server option to cwipc_forward #151

Closed
jackjansen opened this issue Oct 18, 2024 · 1 comment
Closed

We need a --server option to cwipc_forward #151

jackjansen opened this issue Oct 18, 2024 · 1 comment
Assignees

Comments

@jackjansen
Copy link
Contributor

This would be a server mode, which starts streaming compressed point clouds as soon as it is connected to, and that can stream to multiple connections.

We can then fire this up on the external server, and it can be used as a point cloud source by anyone.

Point clouds need to be "retimestamped".

@jackjansen jackjansen self-assigned this Oct 18, 2024
@jackjansen
Copy link
Contributor Author

Actual implementation was a change to the cwipc_forward implementation, so it can accept multiple connections, and feed to those in parallel.

When multiple connections are active (but only then) the --nodrop semantics are slightly lowered, so that if one connection is blocked this does not starve the other connections (i.e. point clouds for the blocked connection will be dropped).

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

No branches or pull requests

1 participant