1 / 65

INT222 Internet I - Internet Fundamentals

INT222 Internet I - Internet Fundamentals. Week 1. Outline. Course Overview Internet Architecture Introduction to JavaScript Demo. Course Overview. Course outline https://scs.senecac.on.ca/course/int222 Course standards http://wsong18.wordpress.com/standards/ Academic Honesty Policy

samantha-sheppard
Download Presentation

INT222 Internet I - Internet Fundamentals

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INT222Internet I - Internet Fundamentals Week 1

  2. Outline • Course Overview • Internet Architecture • Introduction to JavaScript • Demo

  3. Course Overview • Course outline https://scs.senecac.on.ca/course/int222 • Course standards http://wsong18.wordpress.com/standards/ • Academic Honesty Policy https://scs.senecac.on.ca/page/academic-honesty-policy • In this course, you will learn web client (front-end) development concepts and techniques, using  JavaScript, HTML and the DOM, and CSS.

  4. Evaluation 6 labs (1 % or 2% each) 10% 3 quizzes (1.5% or 2% each ) 5% 3 assignments (6% + 6% + 8%=) 20% 2 term tests (17% + 18%=) 35% Final exam 30% ---------------------------------------------------- Total 100%

  5. Promotion Policy To obtain a credit in this subject, a student must: • Achieve a grade of 50% or better on the final exam • Satisfactorily complete all assignments • Achieve a weighted average of 50% or better for the tests and final exam • Achieve a grade of 50% or better on the overall course

  6. Communication • Blackboard • My web site: http://wsong18.wordpress.com/ • INT222 course site https://zenit.senecac.on.ca/~emile.ohan/int222/weekly.html • Email: wei.song@senecacollege.ca • Student help hours: http://zenit.senecac.on.ca/~wei.song/ • Office room: Tel -2101

  7. Coordinate with other sections • Common assignments • Common labs (but different due dates) • Common final exams • Similar term tests • Similar quizzes? • Matched lectures • Lecture Slides on my web page • Weekly Notes on INT222 site

  8. Expectation • Mine: • Be present. Practice. • Learning strategy: • Getting the big picture (concepts, framework, architecture) • paying attention to the details (coding, syntax, hands-on) • Memorizing something! • Yours?

  9. Introduce to Internet architecture

  10. About the Internet architecture • The Internet’s architecture is described in its name, a short form of the compound word “inter-networking”. • This architecture is based in the very specification of the standard TCP/IP protocol, designed to connect any two networks which may be very different in internal hardware, software, and technical design. • Once two networks are interconnected, communication with TCP/IP is enabled end-to-end, so that any node on the Internet has the near magical ability to communicate with any other no matter where they are. This openness of design has enabled the Internet architecture to grow to a global scale.

  11. The Internet map : router-based interconnectivity

  12. The Internet Reference Model and the protocol stack • We may mainly deal with application (layer) protocols.

  13. Internet application protocols • Electronic mail category • SMTP, Simple Mail Transfer Protocol • IMAP, Internet Message Access Protocol • POP, Post Office Protocol • Other protocols • HTTP, HyperText Transfer Protocol • HL7, Health Level Seven • LDAP, Lightweight Directory Access Protocol • NFS, Network File System • DHCP, Dynamic Host Configuration Protocol • IRC, Internet Relay Chat • … • Remote login category • Telnet • SSH, Secure Shell • File transfer category • FTP, File Transfer Protocol • TFTP, Trivial File Transfer Protocol • Support services category • DNS, Domain Name System • SNMP, Simple Network Management Protocol • CMOT, Common Management Information Protocol

  14. A port number is reserved for each the services on a server • FTP (file transfer protocol) - usually on port 21 • SFTP (Secure file transfer protocol) - usually on port 22 • SSH (Secure Shell) - used for secure logins - usually on port 22 • telnet - usually on port 23 • http - usually on port 80

  15. Services provided by the Internet • World Wide Web (the Web ) • It is a collection of web pages connected through hyperlinks and URLs. • It is governed by the Hyper Text Transfer Protocol (HTTP) that deals with the linking of files, documents and other resources of the web. • Electronic Mail (email) • Mailing List • File Transfer Protocol (FTP) • Instant Messaging • News Groups • Chat Rooms • Chat

  16. HyperText Transfer Protocol 

  17. What is HTTP  • HTTP, the Hypertext Transfer Protocol, is the application-layer protocol that is used to transfer data on the (World Wide ) Web. • HTTP comprises the rules governing the format and content of the conversation between a web client and server. • HTTP functions as a request-response protocol in the client-server computing model. • It follows a classical client-server model, with a client opening a connection, making a request then waiting for a response until it receives it. • HTTP is stateless. • The server doesn't keep any data (state) between two requests. • Latest version is HTTP 1.1

  18. HTTP transaction

  19. HTTP Request and response messages

  20. Structure of the HTTP request •  A HTTP (client) request consists of text directives, divided in three blocks: • The first/request line contains a request method, the HTTP protocol version used, followed by the path of the document. • The subsequent block represents specific request headers • Gives the server some information about what kind of data is appropriate (e.g., what language, what MIME types) or some data altering its behavior (e.g., not sending an answer if it is already cached). • This block ends with an empty line. • The final block is the optional data block/request body. • Contains further data and is mainly used by the POST method.

  21. An example of HTTP requests • Fetching the root page of developer.mozilla.org, i.e. http://developer.mozilla.org/, and telling the server that the user-agent would prefer the page in French, if possible: GET / HTTP/1.1 Host: developer.mozilla.org Accept-Language: fr

  22. Another example • Sending the result of a form: POST/contact_form.php HTTP/1.1 Host: developer.mozilla.org Content-Length: 64 Content-Type: application/x-www-form-urlencoded name=Joe%20User&request=Send%20me%20one%20of%20your%20catalogue

  23. HTTP request methods

  24. Structure of a server response • Similarly to a client request, a server response is formed of text directives, divided in three different blocks: • The first block, the status line, consists of an acknowledgment of the HTTP version used, followed by a response status codes. • The subsequent block contains responseheaders, giving the client some information about the data sent and ends with an empty line. • The final block is the data block/response body, which contains the data (if any).

  25. An example of server responses • Successful reception of a web page: HTTP/1.1 200 OK Date: Sat, 09 Oct 2010 14:28:02 GMT Server: Apache Last-Modified: Tue, 01 Dec 2009 20:18:22 GMT ETag: "51142bc1-7449-479b075b2891b" Accept-Ranges: bytes Content-Length: 29769 Content-Type: text/html <!DOCTYPE html... (here comes the 29769 bytes of the requested web page)

  26. Another example • A server notification that the requested resource doesn't exist: HTTP/1.1 404 Not Found Date: Sat, 09 Oct 2010 14:33:02 GMT Server: Apache Last-Modified: Tue, 01 May 2007 14:24:39 GMT ETag: "499fd34e-29ec-42f695ca96761;48fe7523cfcc1" Accept-Ranges: bytes Content-Length: 10732 Content-Type: text/html <!DOCTYPE html... (contains a site-customized page helping the user to find the missing resource)

  27. HTTP response status codes

  28. HTTP header fields

  29. HTTP Secure • Hypertext Transfer Protocol Secure (HTTPS) is a communications protocol for secure communication over a computer network, with especially wide deployment on the Internet. • Technically, it is not a protocol in and of itself; rather, it is the result of simply layering the Hypertext Transfer Protocol (HTTP) on top of the SSL(Secure Sockets Layer)/TLS(Transport Layer Security)  protocol, thus adding the security capabilities of SSL/TLS to standard HTTP communications.

  30. Web Technology

  31. Web Technology Basic • The World Wide Web is a system of interlinked hypertext documents accessed via the Internet. The two basic components of the Web are the Web browser client and the Web server. • Three fundamental elements comprise the technology architecture of the Web: • Uniform Resource Locators (URL) • A standard syntax used for creating identifiers that point to Web-based resources. • eg. https://zenit.senecac.on.ca/~int222_141a45/index.html • protocol = https:// • domain name = zenit.senecac.on.ca • path or URI - uniform resource indicator = ~int222_141a45/index.html • Hypertext Transfer Protocol (HTTP) • This is the primary communications protocol used to exchange content and data throughout the World Wide Web. URLs are typically transmitted via HTTP. • Markup Languages (HTML, XML) • Markup languages provide a lightweight means of expressing Web-centric data and metadata. The two primary markup languages are HTML (which is used to express the presentation of Web pages) and XML (which allows for the definition of vocabularies used to associate meaning to Web-based data via metadata).

  32. Web Applications • A distributed application that uses Web-based technologies (and generally relies on Web browsers for the presentation of user-interfaces) is typically considered a Web application. • These applications can be found in all kinds of cloud-based environments due to their high accessibility.

  33. The common architectural abstraction for Web applications • It is based on the basic three-tier model. • The first tier is called the presentation layer, which represents the user-interface. • The presentation layer has components on both the client and server-side.  • The middle tier is the application layer that implements application logic. • The third tier is the data layer that is comprised of persistent data stores.

  34. Front-end web application • The rising popularity of so-called “modern” web apps means that web developers are focusing on writing more and more front-end, or client-side code. Although back-end, or server-side code still plays an important factor, the fact is that web developers are working more directly with HTML5, CSS3, and JavaScript.

  35. The architecture for front-end web application • What is the front-end/client-side doing? • Render UI • Interactivity • Logical requests to server • UI state management • What is the server-side doing? • Authority on request integrity • Accessing/updating DB • Serving data

  36. Web Development • is hard. • You must know at least 3 (often 4) programming languages: • JavaScript • the state and behavior of the frontend • CSS • how things look • HTML • structure of the UI/Document • Server Programming (INT322) • Stateful storage and interaction with other servers

  37. Introduction to JavaScript

  38. What is a Script • A script is a high-level programming language that is interpreted by another program at runtime rather than compiled by the computer's processor (as other programming languages such as C and C++ are). • Some types of languages are client-side scripting languages, affecting the data that the end user sees in a browser window. Other scripting languages are server-side scripting languages that manipulate the data, usually in a database, on the server. • Scripting languages came about largely because of the development of the Internet as a communications tool. JavaScript, ASP, JSP, PHP, Perl, Tcl and Python are examples of scripting languages.

  39. What is JavaScript? • JavaScript (JS) is a cross-platform Web scripting language. • JavaScript always runs inside a host environment (mostly the browser). • JavaScript is a prototype-based scripting language with dynamic typing and has first-class functions. • There is no class in JS (constructors do what classes do). • The object-based language with prototyping: powerful prototypal object-oriented language • In JavaScript every function is actually a Function object.

  40. About JavaScript • JavaScript is one of the world's most popular programming languages . • The role as the scripting language of the WWW. • simple and easy to learn • JavaScript is the world's most misunderstood programming language. • The name, typecasting, used by amateurs, object-oriented,… • JavaScript is, in the future, the most important language you will learn(? Dart?)

  41. JavaScript History • JavaScript was developed in 1995 by Brendan Eich at Netscape, now a division of America Online. • JavaScript started with simple one-liners embedded in HTML. • The JavaScript backlash (incompatibility, …) caused some web projects to completely ban any client-side programming and trust only their predictable and reliable server. • ECMAScript (European Computer Manufacturers Association) was born, making healthier environment. • JavaScript is now used in much more sophisticated ways. • Developers leverage the object-oriented nature of the language to build scalable code architectures made up of reusable pieces. • JavaScript provides behavior, the third pillar in today's paradigm • web pages consist of three clearly distinguishable parts: content (HTML), presentation (CSS), and behavior (JavaScript).

  42. The Present • Today, you can use JavaScript to do all of this: • Create rich and powerful web applications (the kind of applications that run inside the web browser, such as Gmail) • Write server-side code such as ASP scripts or, for example, code that is run using Rhino (a JavaScript engine written in Java) • Create rich media applications (Flash, Flex) using ActionScript, which is based on ECMAScript • Write scripts that automate administrative tasks on your Windows desktop, using Windows Scripting Host • Write extensions/plugins for a plethora of desktop application such as Firefox, Dreamweaver, and Fiddler • Create web applications that store information in an off-line database on the user's desktop, using Google Gears • Create Yahoo! Widgets, Mac Dashboard widgets, or Adobe Air applications that run on your desktop

  43. Front-end Apps Demo The Planetarium Beautiful Web Introduction to the solar system BananBread Web FPS shoorter CSS Tricks Web Animation (using data from 3d body tracking)

  44. Let’s start with JavaScript

  45. Firefox Scratchpad • Why use Scratchpad? • JavaScript always runs inside a host environment (mostly the browser). • To use Scratchpad, go to the “Web Developer” menu (hint for Mac users: look for the “Web Developer” menu under “Tools”). Select “Scratchpad” from that menu, and you’ll get a text editor window. • Shortcut: Shift+F4 • How to run a script: • Enter some code • Select a portion of the code • Choose one of the three commands from the Execute

  46. prompt() • This built-in function (of the Window object) will display a dialog box (Modal window) that prompts the visitor for input. • Gets user input. Rarely used. • Example code: var ok = prompt("Are you OK?");alert(ok);1+2; // Instpct/display executes the selected code, //and the result is put right into your editor.

  47. alert() • Pops up an alert box (Modal window) with a message and an OK button. • Outputs info. • Example code: function sayHello() { alert("Hello from the Scratchpad");}sayHello(); alert("This is alert 2"); alert(42);

  48. console.log() • Shows a message in web console. • Outputs info. • Example code: varsomeObject = { str: "Some text", id: 5 }; console.log(someObject); • View log: • Ctrl + Shift + J to open browser console.

  49. Create/edit/save the source code • Although web client programming allows us to place JavaScript inline or internal to a document , we prefer that you store your JavaScript code in its own source code file. • You can use any text editor, Scratchpad or programmer’s editor. • We suggest that you store your code in the xxx/js folder, and name each source code file by using a .js extension.

  50. Let’s take a look at some syntax

More Related