On Tue, 02 May 2000, Scott G. Miller wrote: <snip> > > The network object maintained a stack of messages, when a message was > > sent it would be added to the top of this stack. The network object > > would simply keep taking messages off the bottom of the stack and call > > the receive() method of the destination node with the message. When the > > stack was empty, the simulation could be considered complete.
> This was the idea I had in mind when I started the simulator too, but this > gets us a workable system now. Oskar, I'd like to start work on a > timestep sim with you in a week or two (after I get the crypto done). I > expect it'll be about a two week job. I have exams at the end of may, and I haven't been to good about school this term, so I may not have all that much time. After that I should be more or less free however, pending that I may have to spend eight hours a day working somewhere (to rich friends of freedom reading: send cash and I promise I will go out to my parents place in Indonesia where I have house staff and absolutely nothing else to do, and work on Freenet 16 hours a day :-) ). > In my proposal, the entire network is a finite state machine, stepped as a > whole. The network is simulated with these steps, one can hold back > packets to simulate latency, deliver chunks per step to simulate > bandwidth. I'm building it on top of another project of my design, Gamora > (http://gamora.org). Its essentially a self-organizing event routing > framework that pretty much makes this an academic excercise. I just need > help to mimic the node behavior (as far as what it does when it receives > messages, and the like). I tried to have a look at gamora and the javadocs, but could not make much sense out of what it does. You don't have an example of a specific real world usage of it, other then the "Waterworks" architecture. > The nice thing about the system is you can transparently insert components > without affecting the rest of the system or doing any extraneous > coding. You can insert a monitor along a link to intercept messages or > dynamically affect network conditions. Or you can insert an > "attacker" into the system at any point, at run time. > > I envision the frontend looking like the GUI currently checked into > Freenet.sim now, plus windows where one can "be a client" to insert a new > message, and then follow that UniqueID through the system, watching each > node light up when it receives it, as well as get timing > statistics. Because its a timestep simulator, one can pause, fast > forward, play in real time, perhaps even rewind the simulator. I don't see rewind happening. In many ways, the perfect Freenet would be designed so that rewind was theoretically impossible... > > scott > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.1 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE5DhohpXyM95IyRhURAprzAKCn8u1NBW81/0BqCDP+04UtC5pFGwCdFhCs > ZNOiZxytVWnEXtE8LyeSz44= > =M2EA > -----END PGP SIGNATURE----- > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev -- Oskar Sandberg md98-osa at nada.kth.se #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
