Re: object oriented Squid ?

--MimeMultipartBoundary
Content-Type: text/plain; charset=us-ascii

   
  Henrik wrote:
     miguel a.l. paraz wrote:
> The eternal "shall we rewrite Squid from scratch" question :-)
  
  Well some things is possible as a incremental effort:
  
  * Write comments describing the code, where it is not obvious.
  * Document the state machines, and how they relate to each other.
  
  This would make the live easier for everybody, and in large parts can be
  done while learning how squid fits together..
  
  Any ideas for a good notation for describing the state machines?
  
  A proposal on how to get started on documenting the code:
  
  If you find a pice of the code that you can't understand what it does
  (or which looks strange), write a notice in the code that it needs to be
  explained, and send this as a patch to squid-dev, then if someone cares
  to explain, do it as a comment in the code.
  
i admit quietly, from the non-coding sidelines
that i'm much happier hearing about such directions
in the shape of documenting and thinking about the code
than i am about c++ or java-ing squid into oblivion

i don't code
but i engage in the dynamics enuf coding projects
and my impression
is that c++ is way cool
if you're willing to spend the effort
and are more interested in a software engineering endeavor
than a high performance code
but i get the impression
that c++ can really cost you
in terms of what's happnening in the
'protected' (*cough*) chassis part
which has been canonically-implemented
by folks more interested in language
than performance

so folks who needed performance
have often found themselves
having to rip up the c++ internals (eg event handling)
to sustain the thruput etc they need
(which takes Even More Very Dedicated Coding
than your worst nightmares might imagine
with cleaning.up/revamping the C)

that worries me
and until i hear real-life ISP-code
experience narratives o/w
i'm inclined to paranoia

since itfa
i do need this stuff to work at a
bizzy bizzy NAP
sometimes

vrrroom vrrroom

and as you've all re-re-re-re-noted
we don't have lots of DW's to spare

further disambiguation: i'm in a bind (npi)
cause we'd Like to support squid coding ad infinitum
(yum yum)
but the reality is
we're in US federal tax dollars space here
and it has limitations
i.e., we need to focus Lots more on
Internet architecture and globally commercial viability
(and more elegant integration with dns, security,
multicast, isp-compatible pricing, bgp-NG,
hit-metering, URNs (if they ever decide to exist),
optimal server location, robust interoperability,
cache-traffic-flow level routing/traceroute/diagnostic/debugging)
rather than software coding/support/tweaks
than we have so far

DW has indulged
cause he wants to keep his constituency happy
and so do i
(you all are intoxicating :) )

but frankly can't hold out much longer on this folks
without commercial or at least non-NLANR support
to sustain the coding-related effort

www.cygnus.com/www.isc.org/elsethings are possibilities
we can think about
but just need to alert you
the NLANR side of this
really wants to do whatever you want us to
but doesn't have the resources
and likely won't get them from taxes much longer :(

hmmm
think think think
k

--MimeMultipartBoundary--
Received on Tue Jul 29 2003 - 13:15:44 MDT