On Thu, Aug 03, 2000 at 10:32:36PM -0500, Brandon wrote: > > > Yeah, this is really what I am trying to do with nfreenetd. Of > > course, most people won't have to run nfreenetd (and many of these > > people are going to be Windows users, so they can't use nfreenetd), > > but the there are always going to be Unix/Linux speed-junkies who are > > running nodes with massive datastores and large pipes. > > Yeah, I think that's great. There will be people that no matter how long I > lecture them, will still say "But...it's in JAVA!" so it's good to have an > alternative that just says "We are fast! We are in C! We use an SQL > database!" so that they will leave us other developes alone.
Heh. But then, speed may matter if you have large HTLs do to the combined overhead of all the nodes your request is going through. Of course, all this falls into the category of being a bunch of opinions. Another good reason for a fast node is that it will take up less CPU time while you play Quake III. ;) > It's important to maintain total standards compliance, though. You should > never, ever change the protocol and, if possible, keep the same config > file. I know, multiple implementations using the same config file? Who has > ever heard of that? Well it would be a whole new world of standardization > if different node writers could avoid extensions. Of course, the URL of > the JDBC database and that sort of thing are specific to the > implementation. That would go in a secondary, different config file. Oh, > and maybe even the same command-line arguments and syntax? Maybe I am just > dreaming a happy dream. Well, I might put in compatibility with the config files used by the Java nodes, but I am probably going to have another config file such as /etc/nfreentd.conf which is specifically for nfreenetd. As for stuff like command line syntax, nfreenetd is meant to be started up with something such as the SVR4 style run level system, not from the normal user command line. Ultimately, I want nfreenetd to be used like any other Unix network service daemon. As for protocol standards compliance, I will make sure that the *protocol* used by nfreenetd will stay the same, but other behavior such as the criteria for deleting files from the datastore may differ from that in the Java node. For example, nfreenetd will not have a fixed number of files that it can store data on (even if they are not in the datastore). -- Travis Bemann Sendmail is still screwed up on my box. My email address is really bemann at execpc.com. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 2235 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20000803/643976e2/attachment.pgp>
