fproxy can now be launched automatically when the node starts, like in 0.3.
To try it out append attached .conf file fragment to your freenet.conf file. You might have to change the port line if you are running something else on 8888 (e.g. fcpproxy). Known Issues: - file uploading isn't supported yet - splitfiles aren't supported yet Tavin, and Oskar: Here are some notes on the modifications I made to Freenet.client.SegmentOutputStream in order to make InternalClient work reliably. These changes are checked in. // Hacks to make InternalClient work. // There are two issues: // 0) InternalClient writes past the end of the // retrieved document size. The InputStream // used to source the data in SendData.receive() // appears to be 0 padded to multiples of the // part size. I worked around this problem // by having nextBucket() return a NullBucket // to catch the overflow. // 1) InternalClient uses the TransferCompletedEvent // from the SegmentOutputStream to decide when // to transition to the DONE state. The problem is // that with the overflow bytes from problem 0) // the InternalClient can transition to DONE // before the OutputStream for the destination // bucket is flushed. The code immediately below // explicitly flushes and closes the OutputStream. // // Revisit these hacks if/when InternalClient is // cleaned up. -- gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: fragment.conf URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20010917/808212cc/attachment.ksh>
