Skip to main content

New Manifest Attribute support in Summer13 release for Offline Caching Of Data

Offline caching of data is very important feature .This feature is commonly required in mobile applications where we would like the pages to be cached locally in the browser ,so that user can browse through this pages even if the application goes offline temporarily due to network failure .

HTML 5 came with a manifest file concept where the files and pages to be cached in the browser are specified in a text file which is kept in the same server domain as the other pages .This file is basically a text file of content type is text/cache-manifest.

W3schools is a place where i learn basics .Thanks to w3schools for presenting content in simple language .Here is the reference link for all the enthusiastic. 

The App-cache concept is clearly explained on the link above . Summarizing ,its just the manifest file of type text/cache-manifest that tells the browser on the content that will be cached in the server. 

<html manifest="demo.appcache"> 

The html has an attribute to indicate the manifest file .An example shown above where demo.appcache is the text file that holds resources that will be cached once there is no network and still you can access content that's cached on the browser .

Visualforce had some new attributes in recent summer13 and a mainfest attribute was provided in <apex:page> tag to specify manifest file .

This small write up will take you through a very small tutorial where we cache a page and make it accessible even when the browser  is offline .

Lets begin step by step

1)We will first create a page that will be html5 and also specify the manifest file in that page 

Here is the simple visualforce page we create first and lets name it as test

<apex:page doctype="html-5.0" manifest="/apex/CacheManifest" showheader="false" sidebar="false" standardstylesheets="false">  <header>   <h1>  Congratulations!</h1></header> <article>    This page looks almost like HTML5! </article> <img src="/img/seasonLogos/2013_summer_aloha.png" /> </apex:page>

2)The manifest file can also be created from the visualforce page .Naming the page as "CacheManifest"

<apex:page contentType="text/cache-manifest" applyHtmlTag="false" standardStylesheets="false" showHeader="false">CACHE MANIFEST#img/img/seasonLogos/2013_summer_aloha.png</apex:page>

3)Open the visualforce page /apex/test and go offline by disconnecting the network.

Try refreshing and you will see even if your computer has no network still this page will exist due to browser caching of the image .

Here are the some of the snapshots i took from my pre-release org to demonstrate this feature

Observe in chrome how i view the cached resources using the inspect element utility provided by the chrome .

Now let me go offline and view the same page

One thing to note on this is html5 app-cache is  insecure and hence for enterprise applications where data security is primary consideration to develop offline applications this is not the suggested way .

Still this is popular when you want to store some pictures and small data in browser cache for offline .

 Thanks to Bob Buzzard for answering my query on stackexchange  and that had solve the issue of specifying CACHE MANIFEST.


Popular posts from this blog

Invoking Apex Callout From Process Builder

Process builder is GA in Spring 15 and one of the queries I came across was around how to invoke apex callouts from Process builder .

Before process builder came we had two common approaches of calling webservice 

1)We have outbound messages as one of the Actions for workflows.This works if other party implements the WSDL that is generated once Outbound messaging is defined with appropriate end point .

2)Most of times future method invoked through triggers allowed to do apex callouts and invoke external web service provided the future method is annotated with @future(callout=true).This provides lot of flexibility and one of the best approaches .

3)Flow triggers was in BETA and this was also one of the ways we could invoke callouts provided the Flow implements process plugin .To understand in detail how to implement process plugin refer to the below example

The purpose of this blogpost is to demonstrate the new possibility of invoking apex callout through Process Builder 

I tried initi…

Opening Modal Using Lightning Component Framework of SFDC

One of my friend from India threw a challenge .The challenge was to open a modal by using latest and greatest lightning components framework and modals design from SLDS .For the love of community I thought of sharing the entire code base that I did .

So here we start ..

Business Use Case - Need a handy SalesLeader board component that can be used to display the Sales revenue generated by each sales rep for current year in the order of decreasing total revenue .On click of the tile ,we will show detail opportunity list aggregating the revenue .

The component can be dragged in lightning design experience or in App builder lightning Page .

Video Demonstration-

SalesLeaderBoard from Mohith Kumar Shrivastava on Vimeo.

Frameworks Used -
Lightning Design Systems (SLDS) for CSSLightning Component Framework for client side logicApex aura enabled class for backend logicApproach
The component hierarchy is very important to imagine or mindmap before we dig deeper- SalesLeaderMain

Writing Test Classes For Apex Rest Service

I came across a question in a developer community on how to write Unit Test Classes for the Rest API service for POST HTTP calls

Unit Test Classes for REST API following link is very useful and inspired by this jeff had an article on his blog on how to write the test method for same .

Here is the Jeff Blog Link Test Class for REST API(Good reference for GET Rest Services)

In one of my previous blog post i demonstrated how to use native parsing technique for Rest api for User Defined Type
I wrote the Test class for the same and this post is helpful for all those searching for how to write test classes for apex rest service annotated with POST Call
Here is the Rest Service Class for which i attempted the test class
@RestResource(urlMapping='/DemoUrl/*') global with sharing class MyRestResourcedemo { global class RequestWrapper{ public Account acct; public Contact[] cons; } global class ResponseWrapper { public String StatusCode; …