This document provides an introduction to HTML5 and summarizes its new features. It describes the new HTML5 doctype, new semantic elements like header, nav, section and article, new form input types like color and date, support for embedded video and audio, the canvas element for drawing, the history API for manipulating the browser history, local storage for persistent data, web workers for background processing, and links to additional HTML5 resources. The document serves as an overview of the new capabilities introduced in HTML5.
This document discusses REST theory versus practice. It begins with introducing the two speakers, Subbu Allamaraju and Mike Amundsen. The objectives of the talk are then outlined, which are to understand that REST is a set of constraints that can be knowingly relaxed, work with underlying protocols, and apply sound software engineering. Common REST principles are then explained including identifying resources, using URIs, designing representations, using a uniform interface, and using hypermedia as the engine of application state. An example address book REST API is then demonstrated. The talk concludes by discussing practical considerations when implementing REST including managing concurrency, being creative with URIs, and that IDs alone are not as good as full URIs.
The document discusses various techniques for improving website performance and speed. It recommends prioritizing speed to provide a better user experience with slow networks or expensive data plans. Specific techniques mentioned include minimizing HTTP requests through combining and compressing CSS and JavaScript files, leveraging HTML5 features like application caching, optimizing images, and deferring unnecessary JavaScript loading. The document emphasizes that performance impacts both users and search engines like Google.
The document discusses concepts related to browser UI components and pre-rendering in Firefox and Fennec. It covers topics like nsWebShellWindow, browser.xul, tabbrowser, and GeckoView. It provides an overview of major source files and classes involved in rendering like browser.js, content.js, and DocShell. It also explains concepts like the browsing context, session history, windows, and the relationship between windows, DocShell, and documents.
This document discusses cookies and sessions in PHP. Cookies are used to store small pieces of data on the user's browser and move across pages, avoiding relogging in. Sessions store data on the server and are more secure. PHP uses the setcookie() function to set cookies and $_COOKIE to retrieve them. Sessions are started with session_start() and use $_SESSION to set and retrieve session variables. Cookies can be used to remember the session ID so sessions persist across browser closes.
This document summarizes a presentation about identities on the web. It discusses the history of identity providers like Microsoft Passport and the rise of OpenID as an open standard for decentralized authentication. OpenID Connect is presented as an easier to implement specification built on OAuth 2.0 that provides a simpler user experience. Issues with OpenID 2.0 like usability and lack of marketing are covered. The role of proprietary solutions like Facebook Connect is also discussed.
This document discusses cookies and sessions in PHP. Cookies are used to maintain state between HTTP requests and can store a small amount of text data in the user's browser. Sessions serve the same purpose as cookies but store data on the server rather than in the browser. The document demonstrates how to create, access, and destroy both cookies and sessions in PHP code. It also compares the key differences between cookies and sessions, such as cookies persisting after the browser closes while sessions do not.
Session and cookies knowledge is very important for a web developer. In these slides we are going to explore basics of Sessions and Cookies in PHP. How to create and destroy a session. How to create and destroy a cookie. How sessions and cookies are stored.
This document discusses using jQuery for building rich internet applications and provides tips to avoid making a mess of projects with jQuery. It recommends choosing jQuery due to its large community and documentation but warns that jQuery can lead to unmaintainable code if not used properly. It provides examples of bad jQuery code that mixes concerns of structure, style and behavior, and good code that uses semantic classes, progressive enhancement, and external templates. The document advises to separate styling from interaction, use semantics, external templates, and learn real JavaScript concepts beyond jQuery.
This document discusses PHP cookies, sessions, and includes/requires. It explains that cookies are small files stored on a user's computer that identify the user. Sessions store information about a user across multiple pages using the $_SESSION variable. Includes/requires insert the code from one PHP file into another before execution. Examples are provided for setting cookies and sessions, incrementing session values, and including external PHP files.