Juliusz Chroboczek wrote: >> Anyway, I digress. Having read through the source code to Polipo and >> produced patches to it I would say that while sometimes following the >> control flow was slightly challenging this was offset by [...] > > Thanks for the kind words.
I too am very happy with Polipo. I write software since years as a hobby, but I've seldomly worked with code written by others and I am rather new to C. For me, Polipo's code is easy to read and I can figure out reasonably quickly what it does. I failed doing the same with other software projects (e.g. Mozilla). This is largely due to reasons pointed out by Will. > [...] > > While what you're saying true in general, it's certainly not true of > the > work of Boutier and Kerneis. CPC is actually originally my work, and > this latest paper is a continuation of some work that I supervised [1] I quickly read through this paper and it sounds interesting. (I admit, I skipped section 6.) How much work do you think would it be to reimplement Polipo using CPC? > That brings us to a different issue -- which is how I would write > Polipo > now, with all that I've learnt over the years. But I've bored you > enough already. Oh please tell us. I am always looking for opportunities to pick up some new ideas and learn some lessons. Greetings Urs ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Polipo-users mailing list Polipo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/polipo-users
