Html5 offline
•
1 like•666 views
This document discusses how to build offline web applications using HTML5 application cache. It begins by introducing offline applications and the browser support for application cache. It then covers checking for browser support, manifest files that list cached resources, and the applicationCache API for updating the cache and handling cache events like downloading, updating and errors. The key aspects are checking browser support, using a manifest file to define cached files, and the applicationCache API to control caching and respond to status changes.
Report
Share
Report
Share
Recommended
Troubleshooting oracle apps
This document discusses three common issues seen in Oracle Applications - large space consumption by the .patch_storage directory after R12 installation, responsibilities not appearing for users after being assigned, and introducing sysadmin zoom functionality using Oracle Forms personalization. It provides steps to clean up the .patch_storage directory, ensure deferred workflow agents are running so responsibilities are visible, and load a personalization file to add zoom functionality in responsibilities details windows.
Tradecloud REST API intro for Buyers
The document provides an overview of the supply chain platform's API for buyers, including authentication, issuing orders, order processes like receiving responses and goods, and support. The API uses standard HTTP methods and JSON payloads. Key endpoints are described for authentication, issuing new orders, attaching documents, reissuing updated orders, receiving and downloading responses, receiving goods, completing, reopening, and canceling orders. Additional sections cover the company, users, environment status, and API support.
Asp.net control
ASP.NET is a web development platform that allows building dynamic web pages using programming languages like C# and VB.NET. It provides components, services and infrastructure for robust web applications. ASP.NET applications are compiled code that uses classes in the .NET framework. The document describes ASP.NET features, advantages, differences from ASP, the page and application lifecycles, and events in the page lifecycle.
Delivering changes for applications and databases @ Azure
This document discusses delivering changes for databases and applications in Azure. It covers introducing the value stream for continuous delivery of databases and applications, and the problem when they are out of sync. It also covers chapters on applications, infrastructure as code, databases, and DevOps practices. The database chapter discusses challenges with databases, the need for automation through source control, migrations vs state-based approaches, and using Flyway for database migrations. Infrastructure chapters discuss physical machines, virtual machines, platform as a service, and serverless computing.
Asp.net life cycle in depth
ASP.NET life cycle guides in a brief tutorial about how : - ASP.NET forms pages to create dynamic yield ASP.NET accumulates the pages progressively
Building restful apis with laravel
Within a short span of time, RESTful APIs have become an integral part of website and web application development. While developing web services, most web developers nowadays opt for these application programming interfaces (APIs) developed based on REpresentational State Transfer (REST) architectural style. Unlike conventional architectural styles, RESTful API facilitates data exchange between web applications through an open and stateless protocol – HTTP. It further uses HTTP requests to GET, PUT, POST, and DELETE data.
Appear IQ - Tutorials Backbone.js
This tutorial teaches how to integrate a Backbone application with Appear IQ's Data Sync module. It covers initializing the AIQ API, defining a custom collection to translate CRUD operations to API calls, making models compatible with AIQ documents, registering listeners to react to remote changes, and running the integrated app on a device. The tutorial uses a sample task management app and mock data to demonstrate integrating each component.
Offline Storage
This is a presentation which i used as a reference for demonstration. You can use this to have a overview of the html5 offline storage feature.
Recommended
Troubleshooting oracle apps
This document discusses three common issues seen in Oracle Applications - large space consumption by the .patch_storage directory after R12 installation, responsibilities not appearing for users after being assigned, and introducing sysadmin zoom functionality using Oracle Forms personalization. It provides steps to clean up the .patch_storage directory, ensure deferred workflow agents are running so responsibilities are visible, and load a personalization file to add zoom functionality in responsibilities details windows.
Tradecloud REST API intro for Buyers
The document provides an overview of the supply chain platform's API for buyers, including authentication, issuing orders, order processes like receiving responses and goods, and support. The API uses standard HTTP methods and JSON payloads. Key endpoints are described for authentication, issuing new orders, attaching documents, reissuing updated orders, receiving and downloading responses, receiving goods, completing, reopening, and canceling orders. Additional sections cover the company, users, environment status, and API support.
Asp.net control
ASP.NET is a web development platform that allows building dynamic web pages using programming languages like C# and VB.NET. It provides components, services and infrastructure for robust web applications. ASP.NET applications are compiled code that uses classes in the .NET framework. The document describes ASP.NET features, advantages, differences from ASP, the page and application lifecycles, and events in the page lifecycle.
Delivering changes for applications and databases @ Azure
This document discusses delivering changes for databases and applications in Azure. It covers introducing the value stream for continuous delivery of databases and applications, and the problem when they are out of sync. It also covers chapters on applications, infrastructure as code, databases, and DevOps practices. The database chapter discusses challenges with databases, the need for automation through source control, migrations vs state-based approaches, and using Flyway for database migrations. Infrastructure chapters discuss physical machines, virtual machines, platform as a service, and serverless computing.
Asp.net life cycle in depth
ASP.NET life cycle guides in a brief tutorial about how : - ASP.NET forms pages to create dynamic yield ASP.NET accumulates the pages progressively
Building restful apis with laravel
Within a short span of time, RESTful APIs have become an integral part of website and web application development. While developing web services, most web developers nowadays opt for these application programming interfaces (APIs) developed based on REpresentational State Transfer (REST) architectural style. Unlike conventional architectural styles, RESTful API facilitates data exchange between web applications through an open and stateless protocol – HTTP. It further uses HTTP requests to GET, PUT, POST, and DELETE data.
Appear IQ - Tutorials Backbone.js
This tutorial teaches how to integrate a Backbone application with Appear IQ's Data Sync module. It covers initializing the AIQ API, defining a custom collection to translate CRUD operations to API calls, making models compatible with AIQ documents, registering listeners to react to remote changes, and running the integrated app on a device. The tutorial uses a sample task management app and mock data to demonstrate integrating each component.
Offline Storage
This is a presentation which i used as a reference for demonstration. You can use this to have a overview of the html5 offline storage feature.
Asp.net event handler
Event handling in ASP.NET involves responding to events that occur at the client or server. Events raised at the client are handled at the server. When an event like a button click occurs, the browser posts the event to the server, which checks for an associated event handler method to execute. Common events include page and control loading, data binding, and user interaction events. Event handlers are coded to respond to specific events and take action. Controls generate events that can be handled using attributes and event handler methods.
Asp.net page lifecycle
This document discusses the ASP.NET page lifecycle. It begins with an introduction to the speaker and their published articles. It then defines the page lifecycle as the period between a page request and response. The main stages of the lifecycle are described as: initialization, load, postback event handling, rendering, and unload. Events occur and corresponding event handlers are called within each stage. A flow chart visualizes the full lifecycle process from initialize to dispose.
ASP.Net Presentation Part1
The document discusses various topics related to ASP.NET including Visual Studio 2005, ASP.NET framework, page lifecycle, controls, validation, user controls, data binding, and common data types. It provides an overview of creating and working with ASP.NET web applications and pages in Visual Studio.
Http pipeline
This document discusses the HTTP pipeline in ASP.NET, including pipeline modes, objects, and extensibility points like handlers, modules, and the HttpApplication class. It covers the classic and integrated pipeline modes in IIS, and how handlers, modules, and the HttpApplication class can be used to customize request processing and generate responses. Key classes like HttpContext that provide request-specific data are also introduced.
Http pipeline
This document discusses the HTTP pipeline in ASP.NET, including pipeline modes, objects, and extensibility points like handlers, modules, and the HttpApplication class. It covers the classic and integrated pipeline modes in IIS, and how handlers, modules, and the HttpApplication class can be used to customize request processing and generate responses. Key classes like HttpContext that provide request-specific data are also introduced.
Page life cycle IN ASP.NET
The document summarizes the page life cycle events in ASP.NET. It describes each of the main events in the order they occur: Page Request, Start, Initialization, Load, Postback Event Handling, Rendering, and Unload. It also includes descriptions of some additional events like PreInit, Init, InitComplete, PreLoad, etc. and explains what occurs during each step of the page life cycle.
Service objects in Rails tests - factory_girl replacement
Service objects provide a way to test Rails applications by encapsulating business logic and hiding implementation details. They represent use cases or scenarios and allow writing tests that are fast, easy to write, and stay in sync with production code by testing below the controller layer. However, extracting existing Rails code into service objects can be challenging.
Cloud Networking
The document discusses automating the deployment and benchmarking of applications on clouds. The goals are to automate deploying a web application on Amazon Web Services (AWS) and Eucalyptus clouds, then measure its performance on each. Puppet, shell scripts, Apache JMeter, GitHub, and a Twitter Bootstrap web application are used. The application is deployed on AWS and Eucalyptus, then tested under different loads. Results show Eucalyptus has lower error rates but AWS has higher throughput. In conclusion, Eucalyptus performance is better when used as an enterprise cloud versus a community cloud like AWS.
Dev Basics: The ASP.NET Page Life Cycle
When a request occurs for an ASP.Net page, the response is processed through a series of events before being sent to the client browser. These events, known as the Page Life Cycle, are a complicated headache when used improperly, manifesting as odd exceptions, incorrect data, performance issues, and general confusion. It seems simple when reading yet-another-book-on-ASP.NET, but never when applied in the real world. In this session, we decompose this mess, and turn the Life Cycle into an effective and productive tool. No ASP.NET MVC, no Dynamic Data, no MoroRail, no technologies of tomorrow, just the basics of ASP.NET, using the tools we have available in the office, today.
Web Quick Start: Exploring the Web Tier
This session aims to give developers the knowledge they need to take the example WQS website and to develop their own website based on it. Kicking off with a quick demonstration of the website, we'll then take it apart bit by bit to expose the underlying architecture, how requests are handled, the WQS API, and how to write new templates and components.
ASP.NET Page Life Cycle
The document discusses the ASP.NET page lifecycle, which begins when a client requests a page from the server. It goes through initialization, loading, validation, event handling, and rendering steps. Key parts of the lifecycle include initializing controls and themes, loading view state and postback data, validating controls, firing server-side events, and rendering the output. Master pages and user controls follow the same lifecycle but are initialized differently and have their events called at different times in the process. The full lifecycle ensures the correct processing and output of the requested page.
HTBYOOFIYRHT RubyConf
This document discusses building an operations framework from scratch if necessary. It recommends using Chef instead if possible. The key components of such a framework would include an API, domain logic, operations implementations, database, and resources to transition between states. Building it as a framework allows others to subclass the core components. Benefits include testability, availability, debuggability, and auditability. Challenges include the work required and integrating with other tools.
Java spring mysql without hibernate(2) (1)
This document provides instructions for building a CRUD web application using Spring MVC, MySQL, and Mustache templates. It describes setting up the necessary technologies, creating controllers and views to handle requests and display data. Specifically, it outlines how to create controllers to handle GET and POST requests, retrieve and set model data, and render Mustache views. It also demonstrates using request parameters, path variables, arrays, lists, and form handling in Spring MVC.
The New & Improved Confluence Server and Data Center
Confluence Server is on an exciting yet challenging journey to deliver its latest platform version (7.0) very soon. Platform releases usually provide us an opportunity to make significant and/or breaking changes to Confluence. While these changes may seem fairly inconsequential at times, they do unlock a huge potential for our team to ship massive improvements, that help your teams get work done faster in Confluence. Given we only ship a platform version every 2-3 years, Usman Khalid, Senior Team Lead for Confluence Server, will take this opportunity to present some important upcoming changes to our vendors, developers and administrators so they have enough time to understand and prepare for the plethora of benefits and features that are packed into this new version of Confluence.
Laravel 5.4
With the introduction of the Laravel 5.4, many new features were introduced. Let’s have a brief idea about it.
Html5 cache mechanism & local storage
The document discusses HTML5 caching mechanisms and local storage. It provides information on application cache, which allows websites and web apps to be cached and accessed offline. Application cache uses a cache manifest file to specify files for caching. It also covers the JavaScript API for application cache and demonstrates how to detect cache updates and swap caches. The document also discusses HTML5 local storage objects (localStorage and sessionStorage) which can be used to store data on the client side in a web browser.
Taking Web Applications Offline
One of the main advantages of web applications is their ease of deployment. The same can't be said about desktop applications. However, desktop applications work without a network connection. While this used to be a deal breaker for web applications, recent developments in HTML 5 and browser plugins such as Flash and Silverlight allow developers to create web applications that work both online and offline. In this session, Matt will demonstrate how to create offline web applications in HTML 5, Silverlight and Air. Also, other factors for offline applications, such as client-side data storage, will be examined in detail.
Offline First with Service Worker
slide for my talk at DevFest Abuja 2015, where I explained the process involved in developing offline first app by leveraging on the power of service worker.
Using html5 to build offline applications
The document discusses features that enable building offline HTML5 applications, including the application cache, online/offline events, localStorage, Web SQL, and indexed databases. It provides details on how each feature works and its advantages/disadvantages for offline applications. The application cache allows offline browsing and caching of files to reduce server load. Online/offline events notify of cache status changes. localStorage provides simple key-value storage, while Web SQL and indexed databases support more complex data but with greater performance costs. The document recommends different features depending on data needs and browser support.
M S Ajax Client Life Cycle Events
The key events during the client life cycle of a page using Microsoft AJAX include the load event of the Application instance for initial requests and synchronous postbacks. When using UpdatePanel controls, the main events are those of the PageRequestManager class, such as beginRequest and endRequest, which allow handling scenarios like canceling postbacks. These events can be handled by adding event name methods to the Application and PageRequestManager classes.
HTML5 Offline Web Application
This document discusses how to create offline web applications using HTML5 application cache manifest files. It covers HTTP response headers, caching strategies, manifest file structure and directives, updating the cache, checking online/offline status, and the application cache API. The manifest file lists application assets to cache and supports caching, network, and fallback rules. Updates require modifying cache busting values or the manifest file itself.
WordCamp Bucharest 2017
Building an E-commerce Progressive Web App with React and WooCommerce
What is a PWA?, PWA E-commerce Showcases (ex. Alibaba), Differences between a PWA and a responsive website, Technologies used to build a PWA, Structuring a PWA with React, Retrieving data from the API and displaying it, UI/UX components, Integrate a PWA in WordPress, Adding advanced features – Web Push Notifications & Offline Mode
More Related Content
What's hot
Asp.net event handler
Event handling in ASP.NET involves responding to events that occur at the client or server. Events raised at the client are handled at the server. When an event like a button click occurs, the browser posts the event to the server, which checks for an associated event handler method to execute. Common events include page and control loading, data binding, and user interaction events. Event handlers are coded to respond to specific events and take action. Controls generate events that can be handled using attributes and event handler methods.
Asp.net page lifecycle
This document discusses the ASP.NET page lifecycle. It begins with an introduction to the speaker and their published articles. It then defines the page lifecycle as the period between a page request and response. The main stages of the lifecycle are described as: initialization, load, postback event handling, rendering, and unload. Events occur and corresponding event handlers are called within each stage. A flow chart visualizes the full lifecycle process from initialize to dispose.
ASP.Net Presentation Part1
The document discusses various topics related to ASP.NET including Visual Studio 2005, ASP.NET framework, page lifecycle, controls, validation, user controls, data binding, and common data types. It provides an overview of creating and working with ASP.NET web applications and pages in Visual Studio.
Http pipeline
This document discusses the HTTP pipeline in ASP.NET, including pipeline modes, objects, and extensibility points like handlers, modules, and the HttpApplication class. It covers the classic and integrated pipeline modes in IIS, and how handlers, modules, and the HttpApplication class can be used to customize request processing and generate responses. Key classes like HttpContext that provide request-specific data are also introduced.
Http pipeline
This document discusses the HTTP pipeline in ASP.NET, including pipeline modes, objects, and extensibility points like handlers, modules, and the HttpApplication class. It covers the classic and integrated pipeline modes in IIS, and how handlers, modules, and the HttpApplication class can be used to customize request processing and generate responses. Key classes like HttpContext that provide request-specific data are also introduced.
Page life cycle IN ASP.NET
The document summarizes the page life cycle events in ASP.NET. It describes each of the main events in the order they occur: Page Request, Start, Initialization, Load, Postback Event Handling, Rendering, and Unload. It also includes descriptions of some additional events like PreInit, Init, InitComplete, PreLoad, etc. and explains what occurs during each step of the page life cycle.
Service objects in Rails tests - factory_girl replacement
Service objects provide a way to test Rails applications by encapsulating business logic and hiding implementation details. They represent use cases or scenarios and allow writing tests that are fast, easy to write, and stay in sync with production code by testing below the controller layer. However, extracting existing Rails code into service objects can be challenging.
Cloud Networking
The document discusses automating the deployment and benchmarking of applications on clouds. The goals are to automate deploying a web application on Amazon Web Services (AWS) and Eucalyptus clouds, then measure its performance on each. Puppet, shell scripts, Apache JMeter, GitHub, and a Twitter Bootstrap web application are used. The application is deployed on AWS and Eucalyptus, then tested under different loads. Results show Eucalyptus has lower error rates but AWS has higher throughput. In conclusion, Eucalyptus performance is better when used as an enterprise cloud versus a community cloud like AWS.
Dev Basics: The ASP.NET Page Life Cycle
When a request occurs for an ASP.Net page, the response is processed through a series of events before being sent to the client browser. These events, known as the Page Life Cycle, are a complicated headache when used improperly, manifesting as odd exceptions, incorrect data, performance issues, and general confusion. It seems simple when reading yet-another-book-on-ASP.NET, but never when applied in the real world. In this session, we decompose this mess, and turn the Life Cycle into an effective and productive tool. No ASP.NET MVC, no Dynamic Data, no MoroRail, no technologies of tomorrow, just the basics of ASP.NET, using the tools we have available in the office, today.
Web Quick Start: Exploring the Web Tier
This session aims to give developers the knowledge they need to take the example WQS website and to develop their own website based on it. Kicking off with a quick demonstration of the website, we'll then take it apart bit by bit to expose the underlying architecture, how requests are handled, the WQS API, and how to write new templates and components.
ASP.NET Page Life Cycle
The document discusses the ASP.NET page lifecycle, which begins when a client requests a page from the server. It goes through initialization, loading, validation, event handling, and rendering steps. Key parts of the lifecycle include initializing controls and themes, loading view state and postback data, validating controls, firing server-side events, and rendering the output. Master pages and user controls follow the same lifecycle but are initialized differently and have their events called at different times in the process. The full lifecycle ensures the correct processing and output of the requested page.
HTBYOOFIYRHT RubyConf
This document discusses building an operations framework from scratch if necessary. It recommends using Chef instead if possible. The key components of such a framework would include an API, domain logic, operations implementations, database, and resources to transition between states. Building it as a framework allows others to subclass the core components. Benefits include testability, availability, debuggability, and auditability. Challenges include the work required and integrating with other tools.
Java spring mysql without hibernate(2) (1)
This document provides instructions for building a CRUD web application using Spring MVC, MySQL, and Mustache templates. It describes setting up the necessary technologies, creating controllers and views to handle requests and display data. Specifically, it outlines how to create controllers to handle GET and POST requests, retrieve and set model data, and render Mustache views. It also demonstrates using request parameters, path variables, arrays, lists, and form handling in Spring MVC.
The New & Improved Confluence Server and Data Center
Confluence Server is on an exciting yet challenging journey to deliver its latest platform version (7.0) very soon. Platform releases usually provide us an opportunity to make significant and/or breaking changes to Confluence. While these changes may seem fairly inconsequential at times, they do unlock a huge potential for our team to ship massive improvements, that help your teams get work done faster in Confluence. Given we only ship a platform version every 2-3 years, Usman Khalid, Senior Team Lead for Confluence Server, will take this opportunity to present some important upcoming changes to our vendors, developers and administrators so they have enough time to understand and prepare for the plethora of benefits and features that are packed into this new version of Confluence.
Laravel 5.4
With the introduction of the Laravel 5.4, many new features were introduced. Let’s have a brief idea about it.
What's hot (15)
Service objects in Rails tests - factory_girl replacement
Service objects in Rails tests - factory_girl replacement
The New & Improved Confluence Server and Data Center
The New & Improved Confluence Server and Data Center
Similar to Html5 offline
Html5 cache mechanism & local storage
The document discusses HTML5 caching mechanisms and local storage. It provides information on application cache, which allows websites and web apps to be cached and accessed offline. Application cache uses a cache manifest file to specify files for caching. It also covers the JavaScript API for application cache and demonstrates how to detect cache updates and swap caches. The document also discusses HTML5 local storage objects (localStorage and sessionStorage) which can be used to store data on the client side in a web browser.
Taking Web Applications Offline
One of the main advantages of web applications is their ease of deployment. The same can't be said about desktop applications. However, desktop applications work without a network connection. While this used to be a deal breaker for web applications, recent developments in HTML 5 and browser plugins such as Flash and Silverlight allow developers to create web applications that work both online and offline. In this session, Matt will demonstrate how to create offline web applications in HTML 5, Silverlight and Air. Also, other factors for offline applications, such as client-side data storage, will be examined in detail.
Offline First with Service Worker
slide for my talk at DevFest Abuja 2015, where I explained the process involved in developing offline first app by leveraging on the power of service worker.
Using html5 to build offline applications
The document discusses features that enable building offline HTML5 applications, including the application cache, online/offline events, localStorage, Web SQL, and indexed databases. It provides details on how each feature works and its advantages/disadvantages for offline applications. The application cache allows offline browsing and caching of files to reduce server load. Online/offline events notify of cache status changes. localStorage provides simple key-value storage, while Web SQL and indexed databases support more complex data but with greater performance costs. The document recommends different features depending on data needs and browser support.
M S Ajax Client Life Cycle Events
The key events during the client life cycle of a page using Microsoft AJAX include the load event of the Application instance for initial requests and synchronous postbacks. When using UpdatePanel controls, the main events are those of the PageRequestManager class, such as beginRequest and endRequest, which allow handling scenarios like canceling postbacks. These events can be handled by adding event name methods to the Application and PageRequestManager classes.
HTML5 Offline Web Application
This document discusses how to create offline web applications using HTML5 application cache manifest files. It covers HTTP response headers, caching strategies, manifest file structure and directives, updating the cache, checking online/offline status, and the application cache API. The manifest file lists application assets to cache and supports caching, network, and fallback rules. Updates require modifying cache busting values or the manifest file itself.
WordCamp Bucharest 2017
Building an E-commerce Progressive Web App with React and WooCommerce
What is a PWA?, PWA E-commerce Showcases (ex. Alibaba), Differences between a PWA and a responsive website, Technologies used to build a PWA, Structuring a PWA with React, Retrieving data from the API and displaying it, UI/UX components, Integrate a PWA in WordPress, Adding advanced features – Web Push Notifications & Offline Mode
MidwestPHP 2016 - Adventures in Laravel 5
With the release of Laravel 5 there are a lot of new toys to play with. We'll cover the new features and how to start using them in your applications. We'll be covering the new directory structure, changes in blade templates, commands and events, form requests, helpers, route caching and middlewares, controller method injection, migrating from Laravel 4, and more! We will also discuss changes to Illuminate packages and the new Elixir, Socialite, and Contracts packages.
Running Microservices and Docker on AWS Elastic Beanstalk - August 2016 Month...
In this session, we introduce you to a solution for easily running a Docker-powered microservices architecture on AWS using Elastic Beanstalk. We will also cover the fundamentals of Elastic Beanstalk and how it benefits developers looking for a quick and scalable way to get their applications running on AWS with no infrastructure work required.
Building a microservices architecture using Docker can require a lot of work, from launching and operating the underlying infrastructure to installing and maintaining cluster management software. With AWS Elastic Beanstalk’s multicontainer support feature, many of these tasks are simplified and abstracted away so you can focus on your application code. AWS Elastic Beanstalk is an easy-to-use service for deploying and scaling web applications and services developed with Java, .NET, PHP, Node.js, Python, Ruby, Go, and Docker."
Learning Objectives:
• Learn the basics of AWS Elastic Beanstalk
• Understand how to use Elastic Beanstalk to run containerized applications
• Learn how to use Elastic Beanstalk to start architecting microservices-based applications
Progressive Web App - Jeff Burtoft at microsoft zaventem 03-10-2016
Jeff Burtoft's slides for his presentation on Progressive Web Apps (PWA) at Microsoft Zaventem on the 3rd of October 2016.
A "lofiAPI": Using open source applications and simple XML to build a library...
Web services allow libraries to share data and resources outside of traditional applications. The document discusses how Montana State University Libraries created a simple API called "lofiAPI" using open source tools like PHP, MySQL, and XML to provide access to library data. It provides examples of other libraries that have created web services, the benefits of the single source, multiple endpoint model, and encourages attendees to experiment with building their own mashups and APIs.
2310 b 15
This document provides an overview and lessons on configuring, optimizing, and deploying a Microsoft ASP.NET web application. It covers using the cache object and output caching to optimize performance, configuring settings at the machine and application level using configuration files, and preparing and deploying a web application by selecting necessary files and sharing assemblies. The lessons include demonstrations and practices for students to apply the concepts.
2310 b 15
This document provides an overview and lessons on configuring, optimizing, and deploying a Microsoft ASP.NET web application. It covers using the cache object and output caching to optimize performance, configuring settings at the machine and application level using configuration files, and preparing and deploying a web application by selecting necessary files and sharing assemblies.
AWS Tech Summit - Berlin 2011 - Running Java Applications on AWS
Presentation on running Java applications on AWS using AWS Elastic Beanstalk. AWS Tech Summit, Berlin, May 2011
Laravel 5 New Features
This document discusses new features in Laravel 5 including changes to the directory structure, Blade templating, commands, events, form requests, helpers, route caching, middleware, controller method injection, changes to Illuminate packages, Elixir, Socialite, contracts, and upgrading from Laravel 4. It also provides an overview of Laravel Homestead, a virtual machine environment for Laravel development that includes PHP, MySQL, and other tools without requiring installation on the local machine.
Progressive Web Applications - The Next Gen Web Technologies
Progressive web applications (PWAs) address gaps in regular web apps and native apps. PWAs use technologies like service workers, the web app manifest, and the app shell model to provide native-app-like functionality while still being web apps. Service workers allow PWAs to work offline through caching strategies. Push notifications and app install banners further enhance the user experience. Libraries like Sw-Precache and Sw-Toolbox help implement service worker caching strategies. Major companies have adopted PWAs to increase user engagement and reduce data usage compared to regular web and native apps. Cross-browser support and business logic limitations remain challenges for PWAs.
Charla desarrollo de apps con sharepoint y office 365
This document discusses developing apps in SharePoint 2013. It covers types of apps from a user interface and hosting perspective. It also discusses development tools like Napa, Visual Studio, CSOM vs REST, and the Cloud Application Model. Demos are provided of SharePoint hosted apps, including using the chrome control, full immersive apps, and app parts. Authentication and authorization with OAuth is also summarized.
Running Microservices on AWS Elastic Beanstalk
Introduction to a solution for easily running a Docker-powered microservices architecture on AWS using Elastic Beanstalk.
Progressive Web Apps 101
A gentle Introduction to the concept of Progressive Web Apps, explaining the key concept needed to build a website/app that works even when your user is on a flaky network.
Spring RestFul Web Services - CRUD Operations Example
CRUD Operations Using Spring RestFul Web Services. Build using Spring, Hibernate, Maven and Eclipse IDE.
Similar to Html5 offline (20)
Running Microservices and Docker on AWS Elastic Beanstalk - August 2016 Month...
Running Microservices and Docker on AWS Elastic Beanstalk - August 2016 Month...
Progressive Web App - Jeff Burtoft at microsoft zaventem 03-10-2016
Progressive Web App - Jeff Burtoft at microsoft zaventem 03-10-2016
A "lofiAPI": Using open source applications and simple XML to build a library...
A "lofiAPI": Using open source applications and simple XML to build a library...
AWS Tech Summit - Berlin 2011 - Running Java Applications on AWS
AWS Tech Summit - Berlin 2011 - Running Java Applications on AWS
Progressive Web Applications - The Next Gen Web Technologies
Progressive Web Applications - The Next Gen Web Technologies
Charla desarrollo de apps con sharepoint y office 365
Charla desarrollo de apps con sharepoint y office 365
Spring RestFul Web Services - CRUD Operations Example
Spring RestFul Web Services - CRUD Operations Example
Html5 offline
- 1. HTML5Offline Web Applications Wilson Chen
- 2. Agenda Introduction Browser Support Browser - applicationCache API Checking for Browser Support Offline/Online Manifest Files applicationCache
- 3. Introduction What is Offline Application? offline cache Why is it important?
- 4. Advantages Offline browsing Speed Reduce loading on server
- 6. How to check? Check if window.applictionCache exists or not if(window.applicationCache){ // the browser supports } else { // it doesn’t }
- 7. Offline / Online Navigator.onLine is a boolean property to indicate online or not online/offline events of window object
- 8. Manifest file manifest lists resoures which browsers will cache for offline use Content-type is text/cache-manifest
- 9. Manifest file CACHE MANIFEST CACHE Serve these files from applicationCache, even if online NETWORK Alway fetch these files from internet FALLBACK Alternate paths to replace resources that can’t fetched
- 10. applicationCache API applicationCache.update() Trigger cache update applicationCache.status
- 11. applicationCache API applicationCache event
- 12. applicationCache API- checking event Dispatched when the user agent is checking for an updatem or attempting to donwload the manifst for the first time. This is always the first event in the sequence
- 13. applicationCache API- downloading event Dispatched when the user agent has found an update and is fetching it, or is downloading the resources listed by the manifest for the first time.
- 14. applicationCache API- updateready event Dispatched when The resources listed in the manifest have been newly redownloaded. swapCache() to swith to the new cache
- 15. applicationCache API- obsolete event Dispatched when The manifest was found to have become a 404 page or 410 page, so the application cache is being deleted
- 16. applicationCache API- cached event Dispatched when the resources listed in the manifest have been downloaded, and the application is now cached.
- 17. applicationCache API- error event Dispatched when The manifest was a 404 or 410 page, so the attempt to cache the appliction has been absorted The manifest hadn’t changed, but the page referencing the manifest failed to download properly A fatal error occurred while fetching the resources listed in the manifest
- 18. applicationCache API- noupdate event Dispatched when the manifest hadn’t changed
- 19. applicationCache API- progress event Dispatched when the user agent is downloading resources listed by the manifest
- 20. Q&A