> * Rename .freenetrc to $HOME/.freenet/node.properties

The proper naming covention for a UNIX configuration file is .xrc where x
is the name of the program. the proper naming convention for a windows
configuration file is x.ini. I don't know about macs. I don't think
anything should go in .freenet other than state information.

> > * Give the client a configuration file also, called
> $HOME/.freenet/client.properties

A client configuration file is a good idea. But the same things apply as
above.

> * Give the node daemon a configuration interface which piggy-backs on the
> socket the node is already listening on.  Currently I will reject any
> connections that are not from localhost, but later we can think about
> remote administration (+authentication).  Configuration is written/read by
> running node from $HOME/.freenet/node.properties.

Why not configure from stdin? And I agree with Scott about the dubiousness
of configuring running nodes. We rejected remote administration many
times.

> * Client configuration is written/read by running client.

For the GUI, sure. I don't know how that would work for the CLI, but it
seems bad.

> * Traditional way of configuring - i.e. by editing configuration file -
> will be unchanged, but GUI interface will allow it to be edited in a GUI
> fashion.

Cool.

> * Initially a node can run without a properties file, but it will sit
> there and do nothing except listen on its configuration interface
> (localhost only).

It should just use the hardcoded default properties like it does now.

> * Node software complies with JDK 1.1 spec, client software complies with
> JDK 1.2 spec.

The CLI client should compile with 1.1 and the GUI should compile with 1.2
OR 1.1 with the Swing library installed.

> * Anything else we can think of.  (Snazzy interface, etc...)

Reuse as much code between the CLI and GUI client as possible. Move any
duplicated code into the client library.

> What is the timeframe for 0.3?

It's hard to tell. People keep adding things.



_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to