Re: object oriented Squid ? (fwd)

---------- Forwarded message ----------
Date: Fri, 28 Nov 1997 20:33:53 -0600 (CST)
From: Alex Rousskov <rousskov@plains.NoDak.edu>
To: Henrik Nordstrom <hno@hem.passagen.se>
Cc: squid-dev@nlanr.net
Subject: Re: object oriented Squid ?

On Sat, 29 Nov 1997, Henrik Nordstrom wrote:

> As A sparetime Squid developer that knows both C and C++ (and a bit of
> Squid too), I must say that there are some other design issues that is
> fare more interesing than rewriting it in C++..

Agree. I was just trying to make a point that having Squid in C++ can
speedup the development of other, more interesting issues.
 
> 1. A Threaded Squid. This would really speed up development since
> threading makes it possible to have a linear flow of control. Keeping
> track of 3 (or more) interrelated state machines is not at all easy. All
> developers makes mistakes here sooner or later (including Duane W).

I agree that having a linear flow of control would help a lot. However, I
do believe that switching to threads will create far more problems than it
will solve. Just take a look at the threaded (in one way or another) code
of Web servers like Apache. I am positive one will spend more time locking
the stuff and debugging the deadlocks than keeping track of "state
machines".

On the other hand, it is possible to achieve "logical" threading with a
proper use of C++. "concurrent" state machines could be made almost
transparent to a developer using a proper design.
 
> 2. Comments in the code, describing what it does, and why...

Agree 100%.

> I don't beleive writing it in C++ alone makes
> Squid much easier to develop.

A good OO design could help adding new modules and algorithms much easier
though...

Alex.
Received on Fri Nov 28 1997 - 18:38:49 MST