Share Using Data Pipelining to Improve Gadget Speed
Wednesday, June 2nd, 2010
Beginning with OpenSocial 0.9, support for a new featured called Data Pipelining was introduced. Pipelining is really simple to implement and can bring a lot of speed and power to your applications. Pipelined requests are sent before a gadget has been loaded so they are significantly faster.
Data pipelining can be used to load all sorts of information from friends lists, remote json data and plain HTML. For this example, I’m showing how to use pipelining to load in HTML to generate a home view more quickly than using gadgets.io.makeRequest() or osapi.http() after the gadget loads. Another option for quickly loading content is to use
This simple gadget that will load the contents of a file and inject them into the DOM using simple JavaScript.
<?xml version="1.0" encoding="UTF-8" ?> <Module> <ModulePrefs> <Require feature="opensocial-0.9" /> <Require feature="opensocial-data"/> <Require feature="views" /> <Require feature="dynamic-height" /> </ModulePrefs> <Content type="html" view="home"> <![CDATA[ <script xmlns:os="http://ns.opensocial.org/2008/markup" type="text/os-data"> <os:HttpRequest key="home" href="http://example.com/data_pipeline.php" method="post" format="text" authz="signed" /> </script> <script type="text/javascript" src="http://example.com/display.js"></script> <div id="target_div"> </div> }]> </Content> </Module> |
The content of display.js simply loads the pre-fetched content into the target_div on the home page view.
function init(){ var home = opensocial.data.getDataContext().getDataSet('home'); if(home && !home.error){ if(home.content != undefined){ document.getElementById('target_div').innerHTML = home.content; } else { document.getElementById('target_div').innerHTML = home.result.content; } } } gadgets.util.registerOnLoadHandler(init); |
The entire “page” that you would want to generate for this display should be passed back as the output from the file http://example.com/data_pipeline.php. The file will be called with as a signed post containing the current viewer $_POST['opensocial_viewer_id'] and owner $_POST['opensocial_owner_id'] user id values along with the other required signature fields.
You can now query your systems to generate the appropriate display. For example, if the owner and viewer are the same, you might show a summary of activity to their account since they last visited the application. If the viewer and owner are not the same, you might display a public view of the owners activity within the application (and possibly promotional material if the viewer isn’t currently a user of the app).
Now that you understand how to 
This morning I decided to follow 
When I finished the Facebook version of 
This week at 