On Sun, Feb 23, 2003 at 02:25:48PM +1300, David McNab wrote: > Hi, > > While FCP is comfortable for most things, it's painfully low-level when > it comes to FEC/splitfiles. > > The logic for FEC/splitfiles is already in Fred, because FProxy uses it.
Yes, but I am very confident that you don't want to do that in C the same
way GJ does it in java (or the same way I do it in python, for that matter).
The problem with "standardising" FEC splitfile download/reassembly, is that
there is multiple different ways of doing it, each with their own pro's/con's,
with no clear winner.
This being said, a RetrieveSplitFile or whatever fcp command would be nice for
getting something runnning (i could have used it this week, actully, but not
having it beat me into actully fixing my code to retrieve properly :-p), but
the lower level interfaces need to continue to exist
> I'd rather use Python http methods to insert/retrieve via fproxy, than
> figure out all the grotty details of FEC/splitfiles and handle that in
> my client classes.
The grotty details aren't actully as difficult as they seem, seriously.
> If people don't like the idea of putting transparent automatic
> FEC/splitfile handling into FCP, then I'll go the http->fproxy route.
>
> How about it, guys? Doncha think FCP could be a little more high-level?
No ;).
- from fish with love
pgp00000.pgp
Description: PGP signature
