Genny Test v0.25, Mon, 2 Apr 2001 23:38:44 +0000

Greetings,
Fixed:
The odd 'connection refused' crash A simple mistake in genny_basic's echo handler The 'gennyrouter.py' file isn't actually supposed to be in there, don't worry about it.
Miscellenous source cleanups.
Some interesting new numerics under the Control service. The control service is used to tickle and maintain the connection between just the two servants. More will probably be added later.
Plans and ideas:
I want to divorce the application layer from the distributed-networking lawyer.
This has the bad effect of making "firewall" rules, (equivalent to ipchains for Linux or blacklist for Gnut), more difficult.
But the main effect I am after follows...
Genny is one distributed networking protocol. Pyng is one distributed networking protocl. Gnutella is one distributed networking protocol.
The application level services (chat, info, file) can be made to work on all of the above protocols _simultaneously_, resulting in one large application-level network comprised of various bits and pieces of smaller networks.
This has advantages.
The networking layer could end up chaotic and made of several different servants running several different networking protocols, and still the application level could be intact. For example, the core routers the network could be DTCP based while the fringes were Pyng and Genny.
Only one protocol for each service has to be decided on and implemented.
A service could conceivably be implemented over straight TCP for the leaves of the network.
I have done no research, but I suspect this would make transition of the network's users to an IPv6 based infrastructure would be much easier.
Boy, this is such a fun idea!
TomG

Home: Genny: Posts