Isn't it time we turned on FEC by default, making it transparent for 
our users to take advantage of it? Using it still seems to be a 
somewhat haphazard process - and now it seems that we are supporting two 
FEC standards.

Ian.

On Tue, Sep 03, 2002 at 01:02:28AM -0400, Gianni Johansson wrote:
> I built a modified version of freenet-ext.jar allow fproxy to FEC decode 
> files inserted with fishes cli tools.
> 
> Just swap the new .jar in for freenet-ext.jar.  
> 
> It's here.
> http://freenetproject.org/snapshots/fish-compat-freenet-ext.jar
> 
> Decoding works.  I haven't tested encoding via fproxy.
> 
> Here are the lines to add to freenet.conf/ini to turn FEC support on:
> 
> fproxy.params.FECDecoder_0_name=OnionDecoder_0
> fproxy.params.FECDecoder_0_class=OnionFECDecoder
> 
> fproxy.params.FECEncoder_0_name=default_encoder
> fproxy.params.FECEncoder_0_class=OnionFECEncoder
> 
> fproxy.params.FECEncoder_1_name=OnionEncoder_0
> fproxy.params.FECEncoder_1_class=OnionFECEncoder
> 
> # Uncomment and set to a directory with a lot of space
> # fproxy.params.tempDir=/usr3/fproxy_tmp
> 
> 
> Note that if you use the new .jar,  you won't be able to decode FEC files 
> encoded using fproxy and the old version.  I don't think this is a big deal, 
> because I don't think many people were using fproxy for SplitFile insertion.
> 
> --gj
> 
> 
> _______________________________________________
> devl mailing list
> devl at freenetproject.org
> http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl

-- 
Ian Clarke                                        ian at freenetproject.org
Founder & Coordinator, The Freenet Project    http://freenetproject.org/
Chief Technology Officer, Uprizer Inc.           http://www.uprizer.com/
Personal Homepage                                       http://locut.us/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20020903/d89f52a6/attachment.pgp>

Reply via email to