Ian Clarke <[EMAIL PROTECTED]> writes: > Shouldn't the datastore be used for this kind of thing? > > Just how are these settings intended to be used?
For FEC one basically needs transactions, i.e. something like 1. request some blocks 2. lock situation 3. count available blocks; if not enough goto 1, or give up 4. assemble file from available blocks 5. unlock situation AFAIK the problem is that Freenet does not provide locking so a block that is available in step 3, may no longer be there in step 4. So the fproxy FEC code kludges that by moving available blocks to a medium which won't remove them under its arse. The answer seems to be some kind of functionality where you can put something in the local store (or order a requested key to get cached there), and be sure that it won't get deleted until time X. This could also be generalised to provide persistence ... Why fproxy needs a temp dir apart from FEC, I don't know. > On Wed, Oct 02, 2002 at 04:20:34PM -0700, Reuben Balik wrote: > > What would be the recommended entries into the > > freenet.ini to fix the following errors: > > > > WARNING: FECTempDir not set in freenet.conf/ini! > > Oct 2, 2002 5:31:55 PM (freenet.node.Main, main): > > WARNING: FECTempDir not set in freenet.conf/ini! > > Oct 2, 2002 6:15:44 PM > > (freenet.client.http.FproxyServlet, QThread-10): > > WARNING: fproxy tempDir not set. > > Oct 2, 2002 6:15:44 PM > > (freenet.client.http.FproxyServlet, QThread-10): > > Set mainport.params.servlet.1.params.tempDir in > > freenet.conf/ini. This error message answers part of your question, Reuben. -- Robbe
signature.ng
Description: PGP signature
