Matthew Toseland wrote: > Immediate priorities: > 1a. Do not do any (synchronous) DNS lookups on PacketSender. > 1b. If: ... > 1c. Implement a watchdog. Every time PacketSender goes around the loop, ... > 1d. Revert Zothar's recent bogus load-balancing changes. > 2. Make a self-mandatory build. > 3. Work on the auto-updater. > 4. Work on GCJ/Kaffe/whatever support.
Any chance of 5. Implement FCP 'ClientGetManifest' primitive? I'm incorporating an FTP server into my 'freenetfs' project, so that windows users (and anyone else who doesn't want to set up freenetfs) can use 'freedisks' as well. Also, there's good windows explorer to FTP integration. The design of this is critically affected by the ability to fetch a manifest via FCP. If I know that such a primitive won't be implemented soon, I'll fall back on a scheme whereby I implement my own manifests as XML keys. But if it will be implemented, I'll use the freenet manifests instead. Cheers David
