Hi Dave, After your excellent work implementing freenet.exe in classical C, here's another quick project needing your attention. In the Windows release, what do you think about enhancing the freenet.exe so that if given the argument '-remoteNode', it doesn't start an actual freenet node, but instead starts Freenet.contrib.fproxy.ProxyServer. This will be a total blessing for those of us (including me now) who run Freenet on a separate dedicated server machine, and want to run FProxy on a workstation which talks FNP to the server (or, more simply, they want to successfully surf on 'http://127.0.0.1:8081/...' without running a node on their local machine. Requirements would be that freenet.exe, upon being invoked with the '-remoteNode': (i) determines its location though using the '_pgmptr' global variable (ii) looks in flaunch.ini to find the FProxy args, mainly 'serverAddress' and 'htl' (iii) puts a modified icon in the task tray, to indicate that it's running in 'fproxy mode'. (iv) instead of starting up Freenet.node.Node, it starts up Freenet.contrib.fproxy.ProxyServer At present, I'm using a shell script which cd's into the freenet directory, then runs fproxy.exe. It does work, but it leaves a running console window (which is something that freenet.exe eliminates nicely). Whaddya think? Cheers David _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/devl
