TCP connection to simulation is one-way only

[tudelft-cns-atm]

TCP connection to simulation is one-way only

[jooste]

Hi,
This is indeed the case. The telnet connection hasn't been developed beyond a very simple implementation yet. Ideally it would work the way you describe, but this requires more than a simple fix. Because stack commands can originate from several different places, where some need their feedback to be sent everywhere, and others the other way around, implementing this correctly would require a formalised way of tracking source and destination of stack I/O.

We also have the wish to change from the several different network libraries that we use now (python socket, QT network, multiproccessing.Connection) to just one library (zmq), which will also make it easier to provide TCP/UDP output streams (e.g., to drive HITL simulations). When we get around to this the stack command origin/destination issue will also be addressed.

[reube]

Hi @jooste I have implemented a relatively simple fix for this on a fork (which we are keeping up-to-date with this upstream repo). I'll tidy and submit a pull request in the next few days - just writing some tests currently. It may represent a useful fix for the time being.

[reube]

Please see #103
@jooste @ProfHoekstra