Quoting Toad <[EMAIL PROTECTED]>: > Current progress: there was a major mess around the time of the merge to > unstable, maybe a bit after. A lot of bugs have been fixed and a lot of > code converted to use NIO more (DataRequests in particular are now sent > asynchronously). The major obvious problem (most of the diagnostics are > OK, it's too early to say what the psuccess ratios are like yet) is that > fetching files from fproxy can take a ludicrously long time to return. > And even if the connection is closed, it continues. So it is pretty easy > to kill the web interface for a long time just by trying to load lots of > files. Thus, there is a choice: > a) Find out why it is taking so long to reply to many requests, or > b) Implement some sort of cancellation notification for fproxy, or > c) Implement fully asynchronous fproxy. > > Any opinions?
>From a pure 'software quality' point of view, fix your bugs first (Choice A), implement new features second (Choices B & C). 'C' sounds like the best bang for the buck from a new feature standpoint. > -- > Matthew J Toseland - [EMAIL PROTECTED] > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. > j. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
