On Wed, Oct 23, 2002 at 12:13:29PM -0400, Gianni Johansson wrote: <> > 2) Initiating a FEC download takes significant resources. By default 5 > threads are spawned for each request. Imagine what would happen to poor fred > if you were to point fproxy at a page with 20 FEC encoded images. > We could do stuff to fix this. i.e. setting a maximum thread limit for all > FEC requests together, writing request components that are capable of > prioritizing requests, etc. I am actively working on these issues but not > for before code freeze.
I don't suppose there is any way I could convince you to try to work with the flexible metadata interfaces this time, so that splitfile support would not be an arbitrary fproxy only feature? That would automatically deal with the threading issue as well. -- Oskar Sandberg oskar at freenetproject.org _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
