Here's a description of the fcp commands I want to add to do FEC 
encoding/decoding.

I have a working implementation with encoder and decoder plugins based on the 
OnionNetworks Java FEC library.  It has JNI native code support for Windows, 
x86 linux and Solaris.  

Unfortunately, I don't have FEC downloading working in fproxy with the new 
code yet.  Otherwise I might have been tempted to do a "full speed ahead and 
damn the torpedos checkin" ;-)

Don't get too hung up on the issue of segments.  Files under 128M won't get 
segmented with the my plugin implementation.

I played around with FCP level 2 like single call "just do it and tell me 
when your done" designs.  I didn't do it that way, because I don't think that 
will work for real applications.  FEC SplitFile inserting / downloading is a 
resource intensive process.  You need fine grain control at the application 
level.


What do people think about the proposal?

--gj

p.s.
I am not igoring the source issue for the OnionNetworks util code.  Somehow 
that got lost between rev's.  Justin is supposed to be coming out with an 
update release with full source pretty soon.  If worse came to worse we could 
just decompile.  We have full human readable source to all the tricky stuff.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: FCP-FEC.txt
Type: text/english
Size: 9272 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20020912/4af2ff75/attachment.bin>

Reply via email to