coditva / udt-c Goto Github PK

When large data is sent, it gets divided into two parts. The first packet is always on its own.

And there is some loss:
24 chars are lost between first buffer returned by udt_recv and the next when packet data size is 1024.

Right now, docs are only what is present in the header files. Make separate docs that can be used easily.

Right now, there is no support for sending timed packets like ACK and Keep-alive etc. ACK is send a complete data segment is sent. This is not the actual UDT behavior.

Here: https://app.codacy.com/app/UtkarshMe/udt-c

Right now, there is no system for the same.

it never works. basic file transfer fails

In all implementations of UDT available online including this one, I only see the client is sending data. When I tried the client receive data, it never gets data. Is there any reason for this behavior in UDT?

update:
To further add even running the sample prog. - https://github.com/coditva/udt-c/blob/master/progs/recvfile.c - the received file is 0 bytes (i.e. the file gets created but the client program receiving the file never gets data on udt_recvfile(). Thus the file has no contents, and the recvfile program never closes/terminates, while the sender has terminated).

Right now, data is just received and put in buffer without any checks.

Right now, only one client can connect to the server at the given socket. If any other client sends the data, it'll either get ignored or worse, overtake the current client.

Right now, the handshake is done, then the client aborts and sends a shutdown packet.
Link: sourceforge

Keep a loss list and send NAKs for lost packets. Keep a sender's loss list for lost packets and re-transmit them when needed.