> All right, let's make the wrapper scripts determine all the > platform-specific stuff. Ultimately for Windows we can have a wrapper > .EXE (as many apps do) so the whole thing is easy to install and use.
That sounds fine. Take the config file name as a command line argument. It can default to something reasonable (like .freenetrc). > > This is a much better idea. But why do you need a -HUP signal that can be > > sent remotely? Why not just have the configurator kill the node process > > and restart it? Unless you're talking about running the configurator > > remotely, which I see no need for. > > Only because, if you are writing pure Java, this is very difficult to > achieve. Pah. It's easy. You can do like the distributed.net RC5 cracker does and have it periodically check for a file whose existence means it needs to exit immediately. > The problem I can see with this is that the node needs to to keep running > after the client stops, and then the link would be severed. In a perfect > world, the client would have a traffic-lights style stop/start button that > automatically starts and stops the node, and when you exit from the > client, the node keeps running. I'd love to do this, but I can't see a > straight-forward way in Java. Yeah, configuring with stdin isn't that great. Just sharing a config file and restarting the node when changes are made is better. It also avoids the problem of how do we deal with changes when there is a connection in progress. No problem, we just drop all the connections and restart with a blank slate. > The above can be the ultimate goal. I'll just leave it out until I can > think of some clever way of doing it. Perhaps the wrapper script can > somehow do all the yucky platform-specific stuff. That's a good idea. > Yes, my plan was to integrate fproxy, not change it (unless it needs > changing). Perhaps the HTTP proxy could either be standalone, or > run as part of the client, at the user's discretion. Perhaps it doesn't > belong in the node. Perhaps it does. fproxy isn't a proxy, it's a servlet. So that's a decision to make, proxy or servlet (both! yay!). I don't think it should go in the node. Just have the launcher thingy be able to launch that too. > If you force users to run nodes, then you will get zillions of people > running a node on a dialup modem for 15 minutes at a time. This would > kill the network. Surely it's better to let them freeload than bugger up > the network. (My facts may be wrong here.) This won't kill the network. That's what the transient option is for. You can freeload AND run a node. You should run a node. _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
