David Owen queried:
Interesting comment - I currently working on a site for a client
that need a database for job opportunities 500+ Jobs to start
with. Which Mike Brackenbridge will be work on for the database work.The client currently hosts the site on a Microsoft server which has
PHP. (Just can’t get them away from the support plan and hosting
the PC chaps have given them)I’m suggesting to just have the jobs section and MySql database run
on our Linux hosting under a domain like jobs.domain.co.uk. So its
like a sub domain of the main domain. Leaving the bulk of the basic
site on the Microsoft server. As we run the hosting this would
mean we have all the tools and full access to the jobs part of the
site and database in a familiar environment.I would be interested in your advice (especially your experience
dealing with Microsoft Servers), if that sounds like good advice
for the client.
I would say that the majority of issues with Microsoft hosting can be
laid squarely at the feet of IIS (Internet Information Server). Since
that’s the only platform that can run real ASP (not counting ChilSoft
ASP or whatever Sun calls it now), that’s where people get stuck in
the quicksand on that platform. [opinion]IIS is a steaming cart-load
of virus enabling technologies.[/opinion] It is also job security for
MCSEs, so it’s not going anywhere quick.
It sounds like you have a great idea – essentially, all that IIS has
to do is serve up a link to your server, where the jobs are. If they
want to get fancy, they can carve an iframe into the page and host it
in a wrapper from IIS. But all the real work would be done in Linux
and PHP and MySQL, where it belongs. 
Seriously, the choice of technology platform has more to do with your
developer’s skill set than anything else. It is completely possible
to make a very professional site in just about anything, if your
developer has the skills and experience to pull it off. I have seen
AppleScript CGIs that did the job famously – and ran for years. But
then there’s the practical questions you have to ask. If this breaks,
who can fix it? If the developer goes under a bus (sorry Mike, I
actually had a client ask me that once!) who can maintain it? Will
the server need to be patched weekly and restarted daily (cough, IIS,
cough)? When hackers break in, will they get anything useful for
their trouble (cough, IIS runs as root, cough)?
Walter
dynamo mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options