-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 09 February 2003 11:13 am, Jay Oliveri wrote: > I'd like to announce that a new fcpput is currently working (more or less) > with normal files as well as FEC encoded splitfiles. > > This program is the result of a major rewrite to various portions of > ezFCPlib especially, so that the client programs (fcpput, fcpget, > fcpputsite) can focus on logic not specific to FCP (record files in > putsite, command line processing, etc). All inserts end up going through > either one of two possible channels, both defined in ezFCPlib/_fcpPut.c. > > This means that if anyone feels inspired to complete fcpputsite, they will > have a much easier time producing better results. This is because *all* > the FCP logic is contained withing ezFCPlib, allowing fcpputsite to focus > on things like keeping record files (for re-starting a site insertion), > processing command line parameters, creating mapfiles (using ezFCPlib of > course), etc. > > If someone who uses the old fcpputsite would like to help out, it would > then free me to complete the key retrieval code (for ezFCPlib mainly, and > fcpget for the curious). I would then incorporate anything redundant into > ezFCPlib along the way. In the end the program should rock. > > Source tarballs: > http://freenetproject.org/snapshots/fcptools-unstable.tgz > > Pre-compiled Win32 binary: > http://freenetproject.org/snapshots/fcptools-bin.zip > > "fcpput --help" for usage instructions. > > The documentation is slightly out of date, and I'll be working on that as > well in the immediate future so that would-be client writers can take > advantage of ezFCPlib, which as far as I'm concerned has been my focus all > along. > > I do have a mental roadmap that describes where I see the library evolving, > and I'll be documenting it on my personal website. The best idea so far is > another layer directly above ezFCPlib to handle queued inserts, multiple > insert threads, inserts across multiple nodes, etc. all making use of the > current ezFCPlib api. Announcements will be made here when more info is > available.
Does it use the node's FEC interface, or does it have its own? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+RpeZx533NjVSos4RAhrSAJ9XlGr/nfZQGGfagcIxd//eyk4vowCfWurM xiPUlhdeMqoczrfWCWdTsLg= =zBN7 -----END PGP SIGNATURE----- _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
