I have code in my local tree that fixes fproxy FEC inserting. In order to get it working I had to move fproxy and nodeinfo onto the same port as outlined in my previous mail:
http://hawk.freenetproject.org/pipermail/devl/2002-September/001052.html (I haven't broken inserting into a separate servelet yet.) I think that this should simplify adding new functionality in the future. It also fixes the problem people (including me!) were having running fproxy off a remote machine. e.g.: http://hawk.freenetproject.org/pipermail/devl/2002-September/001036.html It might cause grief for the installer maintainers since I had to change the way fproxy parameters are handled in the config file. Who is maintaining the windows and *nix installers these days? If I don't hear strong protests I'll check in tomorrow. --gj _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
