I2P Address: [http://git.idk.i2p]

Skip to content
Snippets Groups Projects
Commit 569e2e89 authored by eyedeekay's avatar eyedeekay
Browse files

Router: Remove multhomedb from javadoc

parent 492356d1
No related branches found
No related tags found
2 merge requests!138I2p.i2p 2.4.0 eliminate use sub dbs option - Do not merge until after multihomeDb is merged,!137I2p.i2p 2.4.0 eliminate multihomedb
Pipeline #1191 passed
...@@ -23,17 +23,15 @@ import net.i2p.util.Log; ...@@ -23,17 +23,15 @@ import net.i2p.util.Log;
* are identified by the hash of the primary session belonging to the client who "owns" * are identified by the hash of the primary session belonging to the client who "owns"
* a particular sub-netDb. * a particular sub-netDb.
* *
* There are 3 "Special" netDbs which have non-hash names: * There is one "Special" netDb which has a non-hash name. This is used for the operation of
* router itself and not clients, in particular when acting as a floodfill:
* *
* - Main NetDB: This is the netDb we use if or when we become a floodfill, and for * - Main NetDB: This is the netDb we use if or when we become a floodfill, and for
* direct interaction with other routers on the network, such as when we are communicating * direct interaction with other routers on the network, such as when we are communicating
* with a floodfill. * with a floodfill.
* - Multihome NetDB: This is used to stash leaseSets for our own sites when they are *
* sent to us by a floodfill, so that we can reply when they are requested back from us * It is possible that it may be advantageous some day to have other netDb's for specific use
* regardless of our closeness to them in the routing table. * cases, but that is not the purpose of this class at this time.
* - Exploratory NetDB: This is used when we want to stash a DatabaseEntry for a key
* during exploration but don't want it to go into the Main NetDB until we do something
* else with it.
* *
* And there are an unlimited number of "Client" netDbs. These sub-netDbs are * And there are an unlimited number of "Client" netDbs. These sub-netDbs are
* intended to contain only the information required to operate them, and as such * intended to contain only the information required to operate them, and as such
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment