[Fwd: Re: Apache switching to Scarab]

[Luis Villa <louie ximian com>]

The end of this (discussing the code modularity of bugzilla 2.17.4)
makes me think that maybe we should skip 2.16 and go directly to 2.17-
sounds like it might make some of the bug-buddy stuff much easier.
Anyway... just a random morning thought. :) 

Luis

-----Forwarded Message-----
From: David Miller <justdave syndicomm com>
To: developers bugzilla org
Subject: Re: Apache switching to Scarab
Date: 24 Jul 2003 14:56:21 -0500

On 7/24/2003 3:43 PM -0400, Yannick Koehler wrote:

> Could you explain to me how Bugzilla is modular?  From my experience with it,
> bugzilla is all but modular.  A change at one place require figuring out its
> side-effect because it is exactly NOT modular.
>
> A module is something contained that if you change you can easily know its
> impact because it has defined input and outputs or services.

Bugzilla's code has changed a LOT in the last year.  2.16.x is for the most
part NOT modular.  2.17.1 and onwards have been a little bit, and have
gradually been increasingly so.  The bulk of the code has been getting
moved into Perl module files (.pm) with defined objects, and methods and
properties on those objects.

A Bug is an object (though it's read-only at the moment - being able to
write to a Bug object is on the intended features list).
An Attachment is an object.
A User is an object.
The authentication process is now handled by pluggable modules.
A Search/Query is an object, although the input/output to the Search object
is still a little fuzzy (it still depends on CGI input for example, rather
than taking arbitrary data).  That'll eventually be fixed, too.
-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=louie ximian com>