At 02:54 PM 8/21/00 -0400, Vince Vielhaber wrote:
>On Mon, 21 Aug 2000, Don Baccus wrote:
>> Learning to use AOLserver is going to be harder than writing a
>> bugtracker and associated tools from scratch? I find that hard to
>> believe.
>Learning how to use it is only a tiny part of it. You still have to
>migrate your website to it. It's not a drop in replacement. So
>writing a bugtracker that will fit the environment vs learning a new
>webserver & migrating your website & rebuilding or rewriting custom
>apps ... For the average, busy admin, don't count too heavily on
>the latter. They're more likely to stick with what they know and
>trust regardless of how good something else is reported to be.
So run the development portion of the site on a different server. Who
said anything about migrating the entire postgres site to AOLserver???
>> If it's true, of course they could run Apache, since arsDigita
>> provides a module which implements the AOLserver API in Apache
>> for exactly this reason, thus making it possible to run the
>> toolkit (including the SDM) under Apache.
>
>First I heard of this, but I'd also have concerns of it's reliability.
>It has to be real new.
Yep. Written by Robert Thau, one of the original eight core Apache
developers, under contract to aD.
>And if it fails it's not ars that looks bad,
>it's the site that's running it.
arsDigita gets on average greater than $500,000 to develop and deploy
a website.
If aD deploys one on Apache+mod_aolserver (they paid for the development
of this module) and it falls over, do you really believe aD won't look
bad?
Seeing as they'd very likely be sued, I think you're wrong.
- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.