zaprus - do THINGS with NETWORKS in ZIG

	Commit message (Collapse)	Author	Age
*	Nicer message for no response	Robby Zambito	13 days
\|
*	Handle network blocking well	Robby Zambito	13 days
\|
*	Don't use multi threading where it is not required	Robby Zambito	13 days
\|
*	Last handshake packet uses non 8888 port	Robby Zambito	13 days
\|
*	Complete the handshake	Robby Zambito	13 days
\|
*	Receive and print the response from the sentinel	Robby Zambito	13 days
\|
*	Initial awaiting for handshake response	Robby Zambito	13 days
\| \| \| \| \|	seems like i might be getting my own initial connection? I get a response even without the sentinal running.
*	Start proper connection handshake	Robby Zambito	13 days
\|
*	Move binary back to zaprus	Robby Zambito	13 days
\| \| \| \|	Also clean up the args for the aux functions by computing the type instead of passing it
*	Not using writer	Robby Zambito	13 days
\| \| \| \| \|	Use direct mem copying into the buf instead of writing to it with the writer interface. Probably better to use the writer actually, since this suffers from the same issue with the extra two null bytes.
*	Initial testing of connection message	Robby Zambito	13 days
\|
*	Move sendRelay logic to Saprus struct	Robby Zambito	13 days