lecture4

lecture4 - CSE 135 Server Side Web Languages Lecture # 4...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
CSE 135 Server Side Web Languages Lecture # 4 Server-Side Scripting Environments Friday, August 6, 2010
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CSE 135 Server Side Web Languages Lecture # 4 Server Side Scripting Intro • Server-side scripting offers a balance between complexity and performance – Not as hard as server-modules (or maybe CGI), but not as performance oriented as server-modules • The general idea is to add scripting directives with template files (often thought of as modified HTML files) – The scripted pages are intercepted by a Web server on the way out and the code converted into the appropriate output – generally HTML Friday, August 6, 2010
Background image of page 2
CSE 135 Server Side Web Languages Lecture # 4 Implementing a Server-Side Scripting Language • Consider the idea of writing a special BozoScript server module that looks to see if a file is being requested with an extension .bozo – The server module either intercepts the page, parses and produces or a result or passes it on without parsing – The trigger for interception is generally a file extension, though some may foolishly intercept anything by setting interception on .html • Good because it hides implementation, bad because you may parse something you don’t need to Friday, August 6, 2010
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CSE 135 Server Side Web Languages Lecture # 4 How Server-Side Scripting Works Contd. Script Engine File.bozo Web Server Resulting page HTTP Request for file.bozo Browser receives response with appropriate MIME type (usually text/html) and renders Script engine intercepts and evaluates “BozoScript” code Friday, August 6, 2010
Background image of page 4
CSE 135 Server Side Web Languages Lecture # 4 Server-Side Scripting Language Characteristics • When looking at server-side scripting languages you see some common characteristics – Syntax variations • Tag like or script like – Focus on troubles of Web programming • Session management, form handling, database programming – Occasionally understanding of separation of programmer, designer, and markup specialists • Through syntax, separation of presentation and logic, etc. – Reliance on external objects for “heavy lifting” Friday, August 6, 2010
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CSE 135 Server Side Web Languages Lecture # 4 Server-Side Scripting Language Characteristics Generations of Server-side scripting? Zero Generation: SSI (server-side includes) 1st Generation: Classic ASP, ColdFusion, PHP 2 nd Generation: JSP, ASP.NET 3 rd Generation: Declarative style- Flex –OR- 4GL like - Ruby on Rails Yet for all their supposed differences server-side scripted environments suffer from an exchange of ease for scalability and performance, some also suffer from portability being tied to a particular platform. The main thrust of 2 nd generation efforts being performance and/or support for larger system development. Oddly the thrust of 3
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/10/2010 for the course CSE CSE135 taught by Professor Powell during the Summer '10 term at UCSD.

Page1 / 82

lecture4 - CSE 135 Server Side Web Languages Lecture # 4...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online