ITEL 302 WEB DEVELOPMENT 3 SERVERSIDE WEB DEVELOPMENT

ITEL 302 WEB DEVELOPMENT 3 SERVER-SIDE WEB DEVELOPMENT

What is Server-Side Web Development? � Refers to software development for applications in which the majority of processing occurs on one or more servers (and not on the client’s machine).

What is Server-Side Scripting? � is a technique used in website design which involves embedding scripts in an HTML source code which results in a user's (client's) request to the server website being handled by a script running on the server-side before the server responds to the client's request. Scripts can be written in any of a number of server-side scripting languages that are available. Serverside scripting differs from client-side scripting where embedded scripts, such as Java. Script, are run client-side in a web browser.

Server-Side Scripting (continued) � Server-side scripting is usually used to provide an interface for the client and to limit client access to proprietary databases or other data sources. These scripts may assemble client characteristics for use in customizing the response based on those characteristics, the user's requirements, access rights, etc. � Server-side scripting also enables the website owner to reduce user access to the source code of serverside scripts which may be proprietary and valuable in it. The down-side to the use of server-side scripting is that the server website computer needs to provide most of the computing resources before sending a page to the client computer for display via its web browser.

History � Netscape introduced an implementation of Java. Script for server-side scripting with Netscape Enterprise Server, first released in December, 1994 (soon after releasing Java. Script for browsers). � Server-side scripting was later used in early 1995 by Fred Du. Fresne while developing the first web site for Boston, MA television station WCVB. The technology is described in US patent 5835712. The patent was issued in 1998 and is now owned by Open Invention Network (OIN). In 2010 OIN named Fred Du. Fresne a "Distinguished Inventor" for his work on server-side scripting.

History (continued) � Today, a variety of services use server-side scripting to deliver results back to a client as a paid or free service. An example would be Wolfram. Alpha, which is a computational knowledge engine that computes results outside the client’s environment and returns the computed result back. A more commonly used service is Google's proprietary search engine, which searches millions of cached results related to the user specified keyword and returns an ordered list of links back to the client. Apple's Siri application also employs server-side scripting outside of a web application. The application takes an input, computes a result, and returns the result back to the client.

Explanation � In the earlier days of the web, server-side scripting was almost exclusively performed by using a combination of C programs, Perl scripts, and shell scripts using the Common Gateway Interface (CGI). Those scripts were executed by the operating system, and the results were served back by the web server. Many modern web servers can directly execute online scripting languages such as ASP and PHP either by the web server itself or via extension modules (e. g. mod_perl or mod_php) to the web server.

Explanation (continued) � Dynamic websites sometimes use custom web application servers, such as the Python "Base HTTP Server" library, although some may not consider this to be server-side scripting. When designing using dynamic web-based scripting techniques, like classic ASP or PHP, developers must have a keen understanding of the logical, temporal, and physical separation between the client and the server. For a user's action to trigger the execution of server-side code, for example, a developer working with classic ASP must explicitly cause the user's browser to make a request back to the web server. Creating such interactions can easily consume much development time and lead to unreadable code.

Explanation (continued) � Server-side scripts are completely processed by the servers instead of clients. When clients request a page containing server side scripts, the applicable server processes the scripts and returns an HTML page to the client. For example, an ASP page is not processed by the browser; instead it is interpreted by the server which can process ASP scripts and return an HTML page to the client.

Static vs Dynamic Web Pages � Most web pages that you view are not static HTML pages. � Instead they are output from programs that run on servers. (these programs can interact with server resources like database and XML Web services. )

Static & Dynamic Web Content

Dynamic Web Technologies � There are quite a number of different technologies for dynamically generating Web content on servers. ◦ ◦ ◦ ◦ ASP. NET ASP CGI Cold. Fusion JSP PHP Ruby on Rails

Dynamic Web Technologies � All of these technologies share one thing in common: ◦ Using programming logic, they generate HTML+CSS+Javascript on the server and send it back to the requesting browser.

Dynamic Web Technologies (again)

What is NOT a Dynamic Server Technology? � Normal Javascript is NOT a dynamic server technology. ◦ Javascript is a simple programming language that is executed by the browser, not the server. ◦ It is embedded within the HTML that is sent to the browser. ◦ It can interact with a server, but it executes after the page is received by the browser.

What is NOT a Dynamic Server Technology � Flash is NOT a dynamic server technology. ◦ Flash refers the shockwave Flash file (SWF) that is sent to the browser. ◦ Your browser, via the Flash Player plug-in, is able to run and display SWF file. � Typically used for advertisement banners, games, or richer user interfaces than are possible with HTML ◦ It can interact with a server, but it executes after the page is received by the browser.

Types of Dynamic Technology � There are quite number of different technologies for dynamically generating web content on the server. � All of these technologies share one thing in common: ◦ Using programming logic they generate HTML on the server and send it back to the requesting browser. � We could categorize dynamic technology into three different types: ◦ Direct Output ◦ Page Scripting ◦ Hybrid

Direct Output � In such a case, programs running on the server directly output HTML back to the client. ◦ CGI and Java Servlets are examples. � Advantage is fast execution time. � Main drawback is that any change in the design of a web page, no matter how minor, requires of intervention of programmer, who must compile the code (and perhaps turn off to server deploy).

Direct Output example public class Hello. World extends Http. Servlet { public void do. Get(Http. Servlet. Request reques, Http. Servlet. Response response) { response. set. Content. Type(“text/html”); Print. Writer out = response. get. Writer(); out. print(“<html>”); out. print(“<body>”); out. print(“<head>”); out. print(“<title>Hello World!</title>”); out. print(“</head>”); out. print(“<h 1>Hello World!</h 1>”); out. print(“</body>”); out. print(“</html>”); } }

Page Scripting � Due to the inefficiences and difficulties in creating direct output web applications, page scripting dynamic content systems have been developed. ◦ That is, scripts embedded within HTML. ◦ HTML for static elements, scripts for dynamic elements ◦ Each page contains the scripts it needs. Examples Microsoft’s ASP, Allaire’s Coldfusion, PHP All of these systems using scripting languages. ◦ These languages are interpreted by the server rather than compile using a compiler. ◦ Advantage: rapid development times for developers. ◦ Disadvantage: slower execution speed.

Example PHP Script <? php require_once (“utilites/header. php”); ? > <? php $current. Time = date (“Fj, Y, g: i a”); $colors = array (‘white’, ’black’, ’green’, ’blue’, ’yellow’, ’orange’); ? > <html> <head></head> <body> <form> The time is now <? php echo $current. Time; ? > <br/> Choose a color: <select> <? For ($i=0; $i<count($colors); $i++) { echo ‘<option>’; echo $colors[$i]; echo ‘</option>; } ? > </select> </form> </body> </html>

Page Scripting � Page scripting systems such as ASP and PHP are great for rapidly developing simple web sites. � They can, however, ◦ be harder to use when creating large, complex sites ◦ be hard to maintain since the code created tends not be object-oriented.

Hybrid � More recent technologies such as Microsoft’s ASP. NET and Sun’s JSP use a hybrid approach and combine the direct and page scripting models. � Disadvantage ◦ Hard to learn compared to page scripting � Advantage ◦ Can use modern software engineering best practices thus making it easier to create large complex sites as well as easier to manage and maintain.

New Approaches to Dynamic Technology � AJAX ◦ Asynchronous Javascript with XML in a new technology that combines dynamic server technology, XML, and Javascript to create web applications or Flash interfaces in their interactivity abilities. ◦ E. g. , Google Maps and Google Gmail. ◦ Dynamic sever technology use to retrieve and generate XML data back to browser. ◦ Browser then temporarily store this XML data and uses Javascript to create richer user interface and retrieve data from XML. ◦ If use changes XML data, it can be sent back to server for more processing.

What do you need for server development? � Web server hardware � Web server software ◦ A server is a computer that serves informaton to other computers. ◦ Obviously needs to be powerful enough to handle the requests. ◦ Software whose purpose is to deliver web content to HTTP requestors.

Web Server Software � Apache ◦ Open source, often on Linux/Unix OS � IIS ◦ Microsoft on Windows

ASP. NET Web Server Options � To test or run ASP. NET Web applications, web server software is necessary. � Microsofts’s production web server software is Internet Information Services (IIS). ◦ In order to run IIS, your computer’s operating system must be one of the following: �Windows �Windows 2000 XP Professional (not XP Home), Vista Business or Ultimate (not Vista Home Basic), Server 2003 Server 2008 7

Visual Studio File Server � One of the advantages of using Visual Studio for ASP. NET development is that your site can be run and tested with or without using IIS. ◦ That is, Visual Studio comes with iits own web server software so that you can test execute ASP. NET pages on the same computer. �The Visual Studio web server can run locally on all current versions of Windows. �The Visual Studio Web server accepts only localhost requests. �It cannot serve pages to another computer, and is therefore suitable only for testing pages locally.

Web Server Options � With Visual Studio, we could say that your computer is a development server (available only to yourself). � Alternately, you might upload your work to a staging server running IIS for team testing. � Of course, if you want others to see this web application, it must eventually be uploaded to a production server (available to your Web application’s audience).