Update Readme.md

CTng/server/Readme.md

@@ -1,15 +1,10 @@
-Monitor_ng.go  
+# Monitor_ng.go  
 
-func Monitor_accuseEntity(c *crypto.CryptoConfig, Accused string) (gossip.Gossip_object, error)  
-//this function accuses the entity if its URL is provided  
+##### Monitor_accuseEntity: this function accuses the entity if its URL is provided   
+##### Monitor_send_to_gossiper: this function send the input gossip object to the gossiper  
+##### Monitor_process_valid_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/revocation information 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_send_to_gossiper(c *MonitorContext, g gossip.Gossip_object)  
-//this function send the input gossip object to the gossiper  
-
-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
+###### func Monitor_handle_gossip: Handles gossip object it received through HTTP