On Sun, Jun 17, 2001 at 05:12:33PM +1200, David McNab wrote: > > Then I passed it on to Dev Random, who has been mostly absent recently. > > So people submit bug reports, but no one feels it's their responsibility > > to fix those bugs. I know that with the rumour of a 0.4 rewrite of FProxy > > I'm certainly not going to waste any of my own time writing code that will > > be trashed. So someone needs to step up and commit to maintaining FProxy. > > OK - I'm willing to be brave (or stupid) and put up my hand, and volunteer > to step in as Mr FProxy. > > Just a coupla points: > 1) Is anyone presently re-writing for 0.4? If so, who?
Not precisely. From the begining the goal has been to place the http interface inside the node for 0.4, which I think everyone agrees is a good thing, since currently fproxy and the node operate inside the same JVM yet communicate via an AES encrypted TCP socket, which is a little silly (see my earlier encrypt-decrypt post). Back in February I though I would get started on doing that, so I poked around inside fproxy and ended up feeling a lot like (no disrespect to Theo and Brandon) when I as a kid went poking around inside a box I had burried a dead bird in a week earlier. So at the time I decided it was better just to put it back in the ground and start from scratch, which is why I wrote some modified Freenet objects (Presentation, RawMessage etc) for HTTP to use as the basis for a more "node present" http interface. Because I was not able to give Freenet the time I had wanted between my trip to SF and the beginning of last week, that effort never really got off the ground. Thanks to Tavin we have now completed the internal client hooks though, so using the InternalClient interface it should very easy to convert programs written for the Client interface in 0.3 to run internally in the 0.4 node. That said, it is my opinion that fproxy should be destroyed (her people taken as slaves, and her land salted so it will never bair crop again). > 2) Can people put up with a delay while I learn the existing FProxy code, > and gain some better Java skills (it'll only take me a week or n)? Honestly, I don't believe there is much there worth salvaging. The http implementation is minimal (all options > /dev/null) and pretty lazy at that (for example Theo lifted the mime implementation from some email client, which generally does the wrong thing quite slowly, putting all data inserted and requested into memory among other things), and the Freenet part is inside the client library anyways. I think there may be some good stuff in the anonymity filter, and maybe the mime-type recognition stuff. > 3) I'm setting up an email filter to put all mails with 'fproxy' in the > subject line into a separate folder, so I don't have to comb through devl > posts. Therefore, I can't guarantee seeing or taking action on any > FProxy-related post that doesn't have the string 'fproxy' in the subject. > 4) Can some devs please brain-dump any known 0.4 FProxy requirements - on or > off list - if on-list, please put 'fproxy' in subject > 5) Any other fproxy wishlist items - please speak up anyone. > > Cheers > David > > ----- Original Message ----- > From: "Brandon" <blanu at uts.cc.utexas.edu> > To: <devl at freenetproject.org> > Sent: Sunday, June 17, 2001 16:49 > Subject: Re: [freenet-devl] FProxy must die^H^H^Hget fixed! > > > > > > > So I'm taking the position now to ask, PLEASE, for FProxy to get fixed > up. > > > > I think the main problem with FProxy being buggy is that it currently has > > no maintainer. It's original author was Theodore Hong. Then I took over. > > Then I passed it on to Dev Random, who has been mostly absent recently. > > So people submit bug reports, but no one feels it's their responsibility > > to fix those bugs. I know that with the rumour of a 0.4 rewrite of FProxy > > I'm certainly not going to waste any of my own time writing code that will > > be trashed. So someone needs to step up and commit to maintaining FProxy. > > > > > > > > _______________________________________________ > > Devl mailing list > > Devl at freenetproject.org > > http://lists.freenetproject.org/mailman/listinfo/devl > > > > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl -- 'DeCSS would be fine. Where is it?' 'Here,' Montag touched his head. 'Ah,' Granger smiled and nodded. Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
