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

Add a command to dynamically add another target IP address for the export stream #6

Closed
jboecker opened this issue Dec 7, 2014 · 1 comment

Comments

@jboecker
Copy link
Member

jboecker commented Dec 7, 2014

When sending DCSBIOS_ADD_EXPORT_TARGET <IP> <PORT> to the import stream, DCS-BIOS should start sending a copy of the export stream to the given IP address and port.

DCSBIOS_REMOVE_EXPORT_TARGET <IP> <PORT> should remove it.

This feature would enable software running on another device on the network to connect to DCS-BIOS without requiring the user to configure anything on the DCS computer. It would also work if the other device has a dynamic IP address (as opposed to the current mechanism of editing BIOSConfig.lua).

@jboecker
Copy link
Member Author

I have implemented this now to start working on #20.
Still need to document this in the Developer Guide.

jboecker added a commit that referenced this issue Oct 22, 2019
…T commands"

This reverts commit ae772c9.

While trying to implement this on the client side it became
apparent that this changeset was not fully thought through.

There is no way to reliably stop exporting to the additional
target IP/Port once that client has been closed. Doing so
would require implementing a keep-alive mechanism.

We have TCP support now, which mostly solves the same problem
in a simpler way (with the disadvantage of a very small
performance penalty).

Additional UDP targets can still be used by statically configuring
them in BIOSConfig.lua.

Closes #6.
jboecker pushed a commit that referenced this issue Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant