Joseph Kowalski wrote: > Perl decision, but I suspect you may find the reason we did this for > Perl was also an exception (one time event) and doesn't apply here.
What do you have against allowing multiple versions of a given component to co-reside in the system? And why should we not reuse and/or update a multi-version model with which we have some experience? I don't think you can argue that we don't need an architecture that supports multiple co-resident versions of a given component in our system, and that we should strive to use it for all instances of the multi-version problem that we come across. I suppose you could argue that SAMPP's components are not ones that should use such an architecture, but I think that that horse is already out of the barn (apache1.3/2.0/2.2.4/..., php4, php5, mysql4, mysql5...) -John
