From 9d5b80ff82a37974dcc5d82c851391b011d99c4e Mon Sep 17 00:00:00 2001 From: Jie Kong Date: Mon, 18 Apr 2022 20:59:59 -0400 Subject: [PATCH] Update Readme.md --- CTng/HTTP/Readme.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CTng/HTTP/Readme.md b/CTng/HTTP/Readme.md index cee4e19..668a908 100644 --- a/CTng/HTTP/Readme.md +++ b/CTng/HTTP/Readme.md @@ -9,6 +9,8 @@ Timer_Loggers TimedMap Timer_Loggers_LastCheckIn int64 (Unix() format) Timer_CAs_LastCheckIn int64 (Unix() format) +Invoke func (c *MonitorContext) InitializeTimedMap() when starting the monitor + If the monitor receives the information (a valid gossip object) from a logger, it will update the Timer from the Timer_loggers with the URL of that logger as the key. If the monitor receives the information (a valid gossip object) from a CA, it will update the Timer from the Timer_CAs with the URL of that CA as the key. If it has been more than 1 MMD since last check in, the monitor will do a linear search on the Timer_loggers, accuse all loggers that didn't repond in this MMD, @@ -24,4 +26,7 @@ func Monitor_process_valid_object(c *MonitorContext, g gossip.Gossip_object) //if the logger sends the sth to the monitor,this function will send the raw version to the gossiper, wait for gossip_wait_time, check its updated PoM database, if the signer of this sth is not in it, threshold sign this sth and send it to the gossiper // Same thing applies to revocation information and CA +//it will store all the valid gossip object from its own gossiper, including different types of PoMs and fully signed sths and revocation information +func Monitor_handle_gossip(c *MonitorContext, w http.ResponseWriter, r *http.Request) +//Handles gossip object it received through HTTP