Tuesday, 23 April 2013

3-6-3 Server-Side and Client-Side Scripting

Server-side Scripting:
  • a users request is fulfilled by running a script directly on the web server to generate dynamic web pages e.g. Google search.
  • code stays on the server.
  • usually used to provide interactive web sites that interface to databases or other data stores.


Security:
  • the source code of server-side scripts are never visible o the browser.
  • these scripts are executed on the server and only send HTML corresponding to the user request.


Web-Server Extension:
  • a program which runs on the server and adds up to date information and function to the web-server.
  • it could add current data such as 'Date' or 'Users Name' to outgoing HTML code.
  • the program could be written in any programming language including C, Perl, Java or Visual Basic.


Common Gateway Interface (Server-side)
  • CGI is a protocol for transferring information between a web server and a web-server extension.
  • the CGI is a set of rules that tells the server how to send and receive information to and from the web-server extension.
  • CGI programs are the most common way for web servers to interact dynamically with users.
  • a common way to provide dynamic feedback for web users is to include scripts or programs that run on the user's machine rather than the web server. This is Client-side Scripting.


Client-Side Scripting
  • run by the viewing web browser (client-side) usually in Java-Script.
  • Client-side scripts allow greater interactivity on a document by responding to use events.
  • for example, a script could be used to check the users' form input prior to submission to provide immediate notice of any errors by the user (validation).

No comments:

Post a Comment