Problem: Require a standard way to determine if a lifecycle is a push triggered lifecycle.

- Both in 1.8 and 2.0 there has always been a need for a framework hook that would allow a developer to know if a particular request was the result
of a push or some user generated request.

- In 2.0 users request can be distinguished from push request by using an input hidden on a page form and then looking for this parameter name in the
requestParamaterMap. This is a bit clumsy and would instead prefer to see that the form at the bottom of the page that is responsible for generating the push to have a param marking the push request as a push. Users could check when needed if this parameter was in the requestParameterMap.

- Application developers could then write a page level phase listener to look for the push parameter and do any push related work before the render
response phase is called.

- In most cases the action event that generated the push request could kick off any application scoped model update. But in most application, session
scoped data would also have to be updated which would have to be deferred to the lifecycle generated by a given push request.

- There is an existing submit parameter called 'ice.submit.type' that might be adapted to provide the necessary information that a push request is being processed. Reference for the existing 'ice.submit.type' parameter: http://jira.icefaces.org/browse/ICE-5832?focusedCommentId=29786&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_29786