Apache 1.3 v. apache 2x front end for zope?
When using apache as a front end for a zope-based cms, are there any significant advantages/problems to using apache 2.0 v. apache 1.3? Rj Robert J. Nagle, Technical Writer Technical Information Services, Texas Instruments, Southwest Freeway MS 702 Stafford TX 77477, 281 274 3989 fax: 281 274 3109
Nagle, Robert wrote:
When using apache as a front end for a zope-based cms, are there any significant advantages/problems to using apache 2.0 v. apache 1.3?
Doesn't seem so. I haven't found any trouble with Apache 2, but no benefits either. They are both huge complicated beasts :-), and they are extremely similar in use. So go with what you feel more comfortable with.
Nagle, Robert wrote:
When using apache as a front end for a zope-based cms, are there any significant advantages/problems to using apache 2.0 v. apache 1.3?
I think I have posted something about my troubles with apache earlier. Maybe not, because I had also troubles with mozilla at that time- so maybe the following is just me ;). Apache2, as it comes with suse 8.1, has shortcomings (read: not-yet-implemented features) which may give some trouble with typical zope usage. The combination on-disk caching, mod_proxy and virtual hosts didn't work. I found a mail on some apache list which confirms this. The problem is it looked ok (files were written in the cache directory etc.) but it never delivered cached content. Nasty one, because it's not too obvious to find that out. When I did find out after much hairpulling that this was indeed not a config error of mine, I apruptly ended my short liason with apache2 and went back to apache1. Newer versions of apache2 might be better, but I as of now I don't need any of the new features, so it's apache1 for me. cheers, oliver
participants (3)
-
Lennart Regebro -
Nagle, Robert -
Oliver Bleutgen