Currently when using the push API functionality for being able to launch/wake-up your application when new push data arrives causes issues in the multiple entry points of a WebWorks application.
The multiple entry points in WebWorks was designed to be used with the Java invoke API. However both the Push services and BBM implementations use a different way of invoking an application when it is closed that bypasses our multiple entry point logic.
Since this entry scenario was not taken into account it can cause multiple issues. One of the side effects that have been seen are possible memory leaks when invoked in this manner.
Further investigation is required to properly support multiple entry points both for the Java invoke API and Push/BBM wake-up scenarios
Overview
Currently when using the push API functionality for being able to launch/wake-up your application when new push data arrives causes issues in the multiple entry points of a WebWorks application.
The multiple entry points in WebWorks was designed to be used with the Java invoke API. However both the Push services and BBM implementations use a different way of invoking an application when it is closed that bypasses our multiple entry point logic.
Since this entry scenario was not taken into account it can cause multiple issues. One of the side effects that have been seen are possible memory leaks when invoked in this manner.
Further investigation is required to properly support multiple entry points both for the Java invoke API and Push/BBM wake-up scenarios