[mnet-devel] playing with routing

[Hauke Johannknecht]

Hi.

it is now possible to route things with zookos great ent router. :)

you just update a _new node to HEAD and start it:
	./Mnet &> _mnet.log &

now you can watch the router establish its peer relations:
	watch -n5 'grep -E "StoreOpHandler|Route" _mnet.log | tail'

you can get a list of all peers considered active routers:
	mnetcli ctl router.list_routing_peers

you can get a list of all known egtp nodes:
	mnetcli ctl router.list_peers

you can send a random generated ping message:
	mnetcli ctl router.thingstore.msgstore.send_ping

this message is injected into routing, and depending on its
(random) id, it may be stored localy or end up on a remote ent peer.

you can see all message-things in your node:
	mnetcli ctl router.thingstore.msgstore.export_msgs

so much for the fun part.

i think i broke the main routing decision thing in ent.Router somehow.
it works, but i am not sure it works as it is supposed to work.
i am keeping a every-minute ping running, so you should see
incoming routed msg-things from time to time.

there is also still the tcpconnection-kills-doq problem. :(
so most likely you wont see any pings within an hour or so.

Must sleep,
  Hauke

-- 
Hauke Johannknecht        Berlin / Germany        HJ422-RIPE
Use PGP ! -> lynx -dump http://www.ash.de/ash.asc | pgp -kaf



-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
mnet-devel mailing list
mnet-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mnet-devel