1. http://wwwis.win.tue.nl/ / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e Web Server Programming 2. Building Applications

2. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e webserver-side-specific development issues Differences with “traditional” software applications: user interface is webpage based choice of programming languages, libraries and tools client/server “ping pong” => need for session management user identification access control, security; resource control issues with debugging and testing

3. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e programming languages and tools which programming languages to use? interpreted vs. compiled portability available libraries available frameworks prototype applications use HTML + hole technology? (e.g. PHP, ASP, JSP) program / server interface? CGI (loose scripts, called by the server on each request) running permanently within server (e.g. PHP, Java servlets)

4. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e web application design (1): context HTTP URLs HTML web server your web application user interface business logic file on disk SQL database another (web?) application (Google?)

5. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e web application design (2): architecture your web application user interface business logic your own code existing libraries / components: parse and create URLs parse and compose HTML talk to a SQL database (…) webpage components

6. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e web application design (3): process outside-in design (for simple applications and prototyping): design a user interface (web pages) supply code to fill the variable bits => fits the “HTML+holes” approach; doesn’t scale inside-out design (for complex or well-known functionality) create a system of functions and objects with relevant functionality (the business logic) add webpages and forms as a user interface to it

7. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e web application design (4): my experiences Petriweb, http://www.petriweb.org/ PHP, no use of libraries (PEAR), some own libraries, HTML+holes approach, difficult to maintainttp://www.petriweb.org/ TU/e-webfilter, http://wwwstijl.tue.nl/filter/http://wwwis.win.tue.nl/~rpost/webprog/ Perl (mod_perl), uses libraries (CPAN, HTML::Mason), some own libraries, web components approach, maintenance is doable http://wwwstijl.tue.nl/filter/http://wwwis.win.tue.nl/~rpost/webprog/

8. / department of mathematics and computer sciencedepartment of mathematics and computer science / architecture of information systems architecture of information systems technische universiteit eindhoven TU/e programming languages and tools too many to even mention: PHP Perl Java JSP ASP ASP.NET ColdFusion Python Ruby Lua XML XSLT SOAP RDF J2EE Typo3 Zope phpNuke Mediawiki JBoss etc. etc. etc. etc. etc. etc. in this course: Java servlets, JSP all the rest: not in this course, sorry use the Web! for software, paper is obsolete