On Tue, 16 Sep 2003, Toad wrote: > On Tue, Sep 16, 2003 at 02:55:54PM -0400, Dan Merillat wrote: > > On Tue, 16 Sep 2003, Toad wrote: > > > > > On Tue, Sep 16, 2003 at 10:52:30PM +1200, David McNab wrote: > > > > This has been discussed before, but it feels right to raise the matter > > > > again. > > > > > > > > I'd like to ask that FCP be updated to transparently handle splitfiles. > > > > > > That would be something other than FCP. FCP is a simple stateless > > > protocol.. something higher level would be useful, but even then, > > > transparent splitfile support is dangerous because it uses massive > > > resources - hence we don't transparently support splitfiles in fproxy. > > > > It'd be better to move a lot of that, including FEC into a C library. > > Why C? Because every other language can then bind to it. That way we > > move the processing burden to the clients but don't force everyone to > > re-implement the wheel. > > Well, there are several C FCP libraries IIRC...
"several" isn't really a resounding answer. I know the fcptools library was doing decently at one point, but what's needed is a Really Good API so FCP can be very low-level and stateless. I'd also prefer things like genSSK and CalcCHK be done outside the node. Why read in a 1mb chunk and feed it to fred when it's faster to do it natively on all platforms? I'm going to grab the fcptools/ezFCPlib and see how far along it is, and see if it's possible to move some of that processing into it. --Dan
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
