3 Commits (7a5a975e4b079c8ced069cb81ca4054cbd475355)

Author	SHA1	Message	Date
Nelson R. Perez	7a5a975e4b	Renamed method and changed its functionality ... - Renamed the 'removeCurrentNodeAndReconnect' as 'reconnectNode' since it will not be removing nodes from the list anymore - Adapted the sample app to work accordingly	2019-06-24 16:07:11 -05:00
Severiano Jaramillo	b6aab142b6	- Added a method to remove nodes from LatencyNodeProvider and implemented a HashSet to keep track of such removed nodes. The reason is that calls to this class are asynchronous and only removing a node from the mFullNodeHeap was not enough to guarantee that it was not going to be added again. ... - Added a isRemoved variable to FullNode class, so that the object can carry itself the removal status information and be able to use the same publish subject to broadcast the status of the FullNode. - Added a method to remove nodes from NodeLatencyVerifier, removed such nodes from pending node latency measurements map 'nodeURLMap' and publish/broadcast the FullNode information with isRemoved=true so that components listening can act accordingly. - Make proper changes to sample app's RemoteNodeActivity so that it removes 'removed' nodes from the list.	2018-11-08 15:14:01 -06:00
Severiano Jaramillo	21311ea5a3	Create RemoveNodeActivity in the sample project that shows an updated list of nodes sorted by latency. This whole activity while be used to add and test the functionallity of removing a node from the nodes list when the app that uses graphenej decides so, and then reconnects to the next best node.	2018-11-08 13:01:09 -06:00