This repository has been archived on 2021-12-05. You can view files and clone it, but cannot push or open issues or pull requests.

kske dcf1b0c58d Send Pending Messages After Successful Handshake (#111) ... Instead of caching pending messages during the handshake and relaying them afterwards, they are now sent after the handshake has been completed. This is possible because the relevant processors (messages and status changes) are now event handlers which are registered at the event bus, which means that they can immediately react to pending messages even if Client#initReceiver has not been fully executed yet. Because Client#initReceiver exists for that very reason, it is no longer necessary anymore. ID generator initialization, which was its other part, is now directly handled in Startup#performHandshake, which is a far more sensible placement. Fixes #106 Reviewed-on: https://git.kske.dev/zdm/envoy/pulls/111 Reviewed-by: DieGurke <maxi@kske.dev>		2020-12-02 21:21:00 +01:00
..
java	Send Pending Messages After Successful Handshake (#111)	2020-12-02 21:21:00 +01:00
resources	Add token-based authentication (without rejection handling)	2020-09-19 11:37:42 +02:00