Server not support MySQL and PHP. What do I lose in web site functionality, if
a) not using a MySQL (search will not necessary in website)
b) not using a PHP (some sort of interaction(request emailing) will be used.You are approaching the problem from the wrong side...
1. Define web site features.
2. See if any of those require server side technologies.
3. Analyse ROI (are those features worth spending extra on hosting with server side scripting enabled)
... on the same token hosting is so cheap nowadays (you can get ad-free hosting with PHP and MySQL for under $100 a year), that it really becomes a mute point ...I have defined features already. Search option is not necessary, at all. So, why use MySQL database if that's not necessary?
Its necessary some sort of interaction(request info- emailing).
Plus some content management system. That's all.
Originally posted by Vladdy
You are approaching the problem from the wrong side...
1. Define web site features.
2. See if any of those require server side technologies.
3. Analyse ROI (are those features worth spending extra on hosting with server side scripting enabled)
... on the same token hosting is so cheap nowadays (you can get ad-free hosting with PHP and MySQL for under $100 a year), that it really becomes a mute point ...Originally posted by Taurus
Server not support MySQL and PHP. What do I lose in web site functionality, if
a) not using a MySQL (search will not necessary in website)
b) not using a PHP (some sort of interaction(request emailing) will be used.
You lose zip. If you don't use it then it doesn't matter at all if it's available or not.Well. Also, is there some way form mailing having avoided server side scripting? And what's with content management system?Both of those can be accompished if you have access to Perl for CGI.
a) not using a MySQL (search will not necessary in website)
b) not using a PHP (some sort of interaction(request emailing) will be used.You are approaching the problem from the wrong side...
1. Define web site features.
2. See if any of those require server side technologies.
3. Analyse ROI (are those features worth spending extra on hosting with server side scripting enabled)
... on the same token hosting is so cheap nowadays (you can get ad-free hosting with PHP and MySQL for under $100 a year), that it really becomes a mute point ...I have defined features already. Search option is not necessary, at all. So, why use MySQL database if that's not necessary?
Its necessary some sort of interaction(request info- emailing).
Plus some content management system. That's all.
Originally posted by Vladdy
You are approaching the problem from the wrong side...
1. Define web site features.
2. See if any of those require server side technologies.
3. Analyse ROI (are those features worth spending extra on hosting with server side scripting enabled)
... on the same token hosting is so cheap nowadays (you can get ad-free hosting with PHP and MySQL for under $100 a year), that it really becomes a mute point ...Originally posted by Taurus
Server not support MySQL and PHP. What do I lose in web site functionality, if
a) not using a MySQL (search will not necessary in website)
b) not using a PHP (some sort of interaction(request emailing) will be used.
You lose zip. If you don't use it then it doesn't matter at all if it's available or not.Well. Also, is there some way form mailing having avoided server side scripting? And what's with content management system?Both of those can be accompished if you have access to Perl for CGI.