GoVector
GoVector copied to clipboard
DistributedClocks
Vector clock logging library for Go
Currently messages are printed to console. Allow for a log file that is used for GoVec messages only (such as error and debug messages).
Currently the FileSub opens and closes the log file every time it writes a message. Change this to leave the file open and close it at the appropriate time. This...
When a publisher disconnects it has maybe dropped out of the distributed system. It would be good to log that as an event with an appropriate vector clock entry. The...
Both publishers and subscribers are being served by the same RPC server (the default), this may mean that a subscriber can make publisher RPC calls and vice versa. Create separate...
Formulate the subscriber API version .1 This should include authentication/nonce bits for setting up the connection. This API should reflect client concerns. Some things that it may contain are: GetOldEvents...
Formulate the publisher API version .1 This should include authentication/nonce bits for setting up the connection. It should also include a set of event types that are relevant to logging...
Formulate the subscriber API version .1 This should include authentication/nonce bits for setting up the connection. It should also include a set of event types that are relevant to advertising...
The broker will need to be parameterized in a number of ways: - IP/port for subscribers (required) - IP/port for publishers (required) - file for file-subscriber (optional) - token for...
Hello! I noticed that when `logToTerminal` is true, `EOF` errors are printed due to line 578. For example, with `go test -v`, output includes ``` === RUN TestSendAndUnpackInt [GoVector]:govec.go:328: TestLogFile-Log.txt...
