- Calling `sq(ubyte[])` now will wake up the condition variable
Receiver
- Calling `rq(ubyte[])` now will wake up the condition variable
- Updated `recvHandlerFunc()` to use the condition variable
- Callind `end()` will wakeup the sleeping thread
- Implemented `ref-string`-based `textpass(ref string)` which can validate and strip at the same time
- Replaced all calls to `isValidText(string)` with `textPass(ref string)`
- Documented a methodClient
- Added some TODOs which need to be done
- When checking for active session use `running == false` not `socket is null` which is not set back to `null` when disconnected after one session
Unit tests
- Added some TODOs which need to be done
- When checking for active session use `running == false` not `socket is null` which is not set back to `null` when disconnected after one session
Unit tests
- Make `running` private and only read-accessile via `isRunning()` method which is available at the package level
- Added todo for `engine` field
Receiver
- Use `isRunning()` now
Sender
- Use `isRunning()` now
- Added an overridable `onConnectionClosed()` that is called when the connection is closed by either us or the remote host
- Added `closedConnectionHandler()` (gonna get rid of soon)
- Calling `disconnect()` will now RATHER shutdown the socket than close it, it no longer performs any other sub-systems clean up
- Implemented `doThreadCleanup()` which stops the receive and send managers, stops the eventy engine too
- At every `read()` we do in the reader loop, check if the return value is `<0` or `==0` in which case set the running state to false and exit the loop
- The exiting of the reader loop will now shutdown the socket (in case remote host caused it and not us (via `disconnect()` for example) ), `close()` the socket and call `doThreadCleanup()`
- Now catches `SnoozeError` if a the libsnooze `Event`'s failed to have their `ensure()` call succeed
ErrorType
- Updated description for enum member `INTERNAL_FAILURE`
Sender
- Removed now-completed TODO
Receiver
- Removed now-completed TODO
- Documented that `initEvents()` may throw an `EventyException`
ErrorType
- Added new member `INTERNAL_FAILURE` which could occur from errors with `Eventy` when setting up the signal handlers and event types
