murphymarkw / c-nydus Goto Github PK

These should be extremely minimal. To start, just have Python call the server methods, which will just block.

Seems to occur sporadically when immediately closing the UDT socket after accepting the connection. Could the UDP layer be dropping it?

To reproduce w/ 5ebffae:

nc -l 9090
nydus
up -v localhost 9000

Run a few times, setting up the nc and up after each run. Will usually work, but occasionally up will hang.

Although TCP / UDT pairing is the current focus, it would be ideal to abstract away the underlying protocol and simply expose a struct that provides the bare minimum necessary to connect any two socket-based protocols in a producer / consumer configuration.

We need it. Preferably argp.

Right now the system is hardcoded to start two servers - a TCP server and a UDT server. Each of these each starts a client type - a TCP client and UDT client. Currently, this is done because there is no argument parsing being done to select the types at runtime.

Ideally, each instance of nydus should only start one server type and one client type. Each of these should be specified at runtime. The server should be given a host and port to listen on, and the client should be given a host and port to which it will forward traffic.

In order to minimize the impedance mismatch of utilizing two different protocols, it would be good to use both epoll and ring buffers to produce async I/O in the translation layer.