I'm making some tests over EndpointRouter and I see there is a
high latency for rerouting procedure, in case of a peer connecting/disconnecting
It seems owing to EndpointRouter route cache, so, although the transport detects
a closure successfully, the related messenger and route persists for a while
(5 minutes?). The rerouting is performed when:
a) Incoming messenger for route is null
b) Outgoing messenger for router is null
c) Destination's class expiration timeout expires or, it's cleared by noOutgoingMessenger expiration, because findReachableEndpoint method in EndpointRouter returns a null Messenger.
I think this latency must to be corrected, or at least the programmer should to
be a procedure to take control of it!