Just thought I'd post about the differences between a serverside language, and a clientside language. Alot of people get them confused easily

Clientside:
Scripts are placed inside a <script> tag in the page. Visitors are able to see the scripts in the source code of the page. The scripts are run on your computer.

Advantages:

• Can do more, e.g. make items move.
• Can perform actions without having to reload the page first.
• Can be used with HTML tags. (e.g. onLoad, OnMouseOver)
• Are used to make rollover buttons, which are an important part of many websites.

Disadvantages:

• Scripts are interpreted at the visitors browser, if their browser is out-of-date the website will not display properly
• Not secure, anyone can look at the code in the page source
• Can slow down old computers
• Some browsers disable active content, such as clientside scripts and tell the user they may be harmful

Some common uses:

• Button rollover effects
• Cursor trails
• Form verification
• Creating cookies

Serverside:
Scripts are placed inside a <? tag in the page. Visitors are not able to see the scripts. The scripts are run at the server, then the result is sent to your computer.

Advantages:

• More secure, visitors aren't able to view scripts
• All scripts are performed at the server, it will work with any browser
• You are able to include external files, to save coding
• You can combine it with programs such as MySQL

Disadvantages:

• Scripts can only be performed when the page loads/reloads
• When moving sites, some code may have to be modified, depending on the configuration and version of PHP
• In most languages, variables must be preceeded with a $ sign
• All lines must end in a semicolon (

Some common uses:

• User management
• File includes
• Database communication
• Finding $_GET variables (e.g. index.php?variable=value)

I hope that helped you decide which is the best for you! So you're less and more !

 

 

 

Reply

Another disadvantage to server side scripting: an out of control script (aka infinite loop) will take down your server. If a client side script loses control, the most that can go wrong is a crashed browser, and your server won't get hurt.

Reply

server side every day. client side bores the hell out of me

Reply

As I like to use content management systems, I am always using server side technologies like php.

Reply

Nice guide.

I'm all for server side too, especially now with ajax you can make very advanced sites that don't even need to reload if it's setup properly - you then also have the advantage of the server doing all the processing so the client just gets the direct html code

-HellFire

Reply

Yeah, the main reason why I use Serverside codes, is because if you had something in JavaScript, it might do one thing in Safari, another in Firefox, and nothing in IE, which is what usually happens... But with serverside it doesn't matter what browser the user has, its what server you have.

Reply

I think serverside is better.

it can do more i think.

Reply