Assigning to mircea to provide the bridge api required. Can assign back to me for doing Android container integration. Once we have that working, we can look at Apple and BB.

The bridge already provides pause and resume APIs for the push connection, so likely the only thing necessary is an ICEfaces bridge method to request a page update.

When we expand further to non-ICEfaces applications, we will likely need to include the pushid in the notification callback, which may or may not be possible on the different platforms.

Made the internal ICEfaces bridge function for retrieving updates public. The function signature is ice.retrieveUpdate(pushID) where the parameter is the pushID that the function will retrieve the update for. The function returns another function that can be called repeatedly, ready to be used as a callback.

Usage:

var updateView = ice.retrieveUpdate(pushID);
ice.push.register([pushID], updateView);

We likely need something with no parameters like

ice.ajaxRefresh()

That will update the current page using ajax. To make this compatible with portlet applications, each view should register so that the above call would result in an ajax update of every view on the page.

This has been added to the Android container, and is working well. Not only less intrusive from the user perspective, but simplifies processing in the container. No longer need to disable the update if user is using the camera for instance. The thumbnail and hidden fields stay intact while the carousel updates when returning to the main activity from the camera.

The native-interface.js files now contain define the function ice.mobiRefresh(). This will invoke ice.ajaxRefresh() if available or window.location.reload if not.

ajaxRefresh was being invoked, but seemed to have no effect on the iPhone, so is now being invoked via setTimeout of 50ms.