[thelist] ASP/open source/static/dynamic sites pro's and con's
Luther, Ron
Ron.Luther at compaq.com
Mon Jan 14 14:29:23 CST 2002
Hi Tony,
I really think we need more information about their demands and
expectations in order to provide any decent 'advice' ... but what the
heck, I'll take a stab at it anyway. ;-)
2. While I generally prefer 'dynamic' to 'static', I really think it's a
decision that should be based on what they are trying to do. E.g. If
all the client wants out of their presence on the web is to put up a
list of contact numbers and the text of some local ordnances then I
really don't see any reason to subject them to a database back-end.
That would seem an unnecessary expense.
1. Expedience. I've always kind of thought that when this was a
decision to be made, (I haven't had that luxury yet - what I see are
tons of "legacy" code that the new stuff has to integrate with.), the
overriding factors would be the degree of client/consultant experience
and expertise with one technology or another. If, for instance, the
client had a really sharp SQL7 dba who was going to handle the database
upkeep then I think it would be kind of silly to try to force them into
a MySQL solution. If the client has no expertise and the web consulting
team has a world-class ASP guru on site, why would they want to build
the site in Python? Make sense?
My 2¢,
RonL.
-----Original Message-----
From: Tony Crockford [mailto:tonyc at boldfish.co.uk]
any thoughts on pros and cons of:
1. ASP vs. Open source solutions
2. Dynamic versus static sites
More information about the thelist
mailing list