<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hi Mitar,<br><br><div>> <br>> Some questions. I would like to better understand your data schema:<br>> <br>> yaffmap_node.isDummy - what and why?<br>> yaffmap_node.isGlobalUpdated - what and why?<br>These attributes have to do with the possiblity to upload a global topology view of a single node to the map server.<br>If there is a node in this view which does not send information by its own to the map server a dummy node has to be <br>created with the limited information that is available. But there may also be the case that a node once had updated <br>its data but does not anymore. But because it still in the topology view of a node in his mesh it can be globally updated <br>but not a dummy.<br><br>> yaffmap_node.replicatedBy - what and why?<br>This attribute holds the ID of the map server this node was pulled from during replication.<br>As said in the first mail, the possibility for decentral operation was an important point.<br><br>> yaffmap_node.agentRelease - what and why?<br>> yaffmap_node.tree - what and why?<br>To make things easier for us we implemented an automatic agent upgrade.<br>With the tree option you can choose whether is should upgrade devel or stable or even special trees communities maintain on their own.<br>The attribute agentRelease is simply the version number of the agent running on the mesh node.<br>On the server side my friend implemented a mapping between compatible server and agent versions. <br>That way the user of the mesh node does not have to care about which agent version he is running. <br>He simply has to configure a valid server.<br><br>Hope this helped<br><br>Regards<br>Dennis<br></div> </div></body>
</html>