summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Use Client as var type instead of singletonpush-sqrvtkyntxqtRobby Zambito5 days
|
* Fix issue returning stack pointerRobby Zambito5 days
|
* Fix extra bytes in connection message.Robby Zambito5 days
|
* Add broadcast initial interest using raw socketsRobby Zambito5 days
| | | | Use this from the relay message
* Update gatorcat dep and use bytes for broadcast messageRobby Zambito5 days
| | | | The latter is helpful for the lifetime of the message.
* Remove allocation for messagesRobby Zambito5 days
|
* Add comments and fix testsRobby Zambito5 days
| | | | | | | Also added networkBytesAsValue and restored bytesAsValue. These are useful for treating the bytes from the network directly as a Message. Otherwise, the init function would overwrite the packet type and length to be correct. I would like the message handling to fail if the message body is incorrect.
* fix use after freepush-tznmzxxxnnozRobby Zambito5 days
|
* Attempt to base64 encode the connection payloadRobby Zambito5 days
| | | | | | For some reason I am still getting this: 2025/05/10 16:37:06 Error decoding message: SGVsbG8gZGFya25lc3MgbXkgb2xkIGZyaWVuZA==::53475673624738675a4746796132356c63334d6762586b676232786b49475a79615756755a413d3daaaa
* Use slice for init, and add better error sets.Robby Zambito5 days
| | | | | The slice sets us avoid allocating within the init function. This means init can't fail, and it also makes it easier to stack allocate messages (slice an array buffer, instead of creating a stack allocator).
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* Remove bytesAsValueUncheckedRobby Zambito5 days
| | | | Callers can instead use std.mem.bytesAsValue directly.
* Cleanup asBytes and test itRobby Zambito5 days
|
* Simplify init interfaceRobby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* Align the bytes instead of the structRobby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* (no commit message)Robby Zambito5 days
|
* Starting real connectionsRobby Zambito5 days
|
* Use FAIL as the default dest if unable to parseHEADmasterRobby Zambito2025-04-27
|
* Add CLI to specify dest for relay messagesRobby Zambito2025-04-19
| | | | The dest can be specified as a 4 char ASCII string, or as an IPv4 address.
* Rename Saprus to Client internallyRobby Zambito2025-04-14
|
* Break out the impl to a libRobby Zambito2025-04-13
| | | | This will make it easier to make a C library.
* Do some things for invyinvyRobby Zambito2025-04-13
|
* Use dynamic array instead of arraylistRobby Zambito2025-04-06
| | | | we know the size (assuming the len is correct) so we can preallocate the whole array
* Depend on clap the same way as networkRobby Zambito2025-04-06
|
* Don't print help after sending messageRobby Zambito2025-04-06
|
* Add comment for cli example referenceRobby Zambito2025-04-06
|
* Allow caller to specify what kind of message to send with argRobby Zambito2025-04-06
|
* Nicer message for no responseRobby Zambito2025-04-06
|
* Handle network blocking wellRobby Zambito2025-04-06
|
* Don't use multi threading where it is not requiredRobby Zambito2025-04-06
|
* Last handshake packet uses non 8888 portRobby Zambito2025-04-06
|
* Complete the handshakeRobby Zambito2025-04-06
|
* Receive and print the response from the sentinelRobby Zambito2025-04-06
|
* Initial awaiting for handshake responseRobby Zambito2025-04-06
| | | | | seems like i might be getting my own initial connection? I get a response even without the sentinal running.
* Start proper connection handshakeRobby Zambito2025-04-06
|
* Move binary back to zaprusRobby Zambito2025-04-06
| | | | Also clean up the args for the aux functions by computing the type instead of passing it
* Correctly handle the endiness and packedness of the the header reading and ↵Robby Zambito2025-04-06
| | | | writing
* Write the header as a packed intRobby Zambito2025-04-06
| | | | this seems like the best way to do it.
* Not using writerRobby Zambito2025-04-06
| | | | | 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 messageRobby Zambito2025-04-06
|
* Move sendRelay logic to Saprus structRobby Zambito2025-04-06
|
* Break relay into a specific programRobby Zambito2025-04-06
|
* Move types to their own fileRobby Zambito2025-04-06
| | | | Make it so I can specify the payload message