[ https://issues.jboss.org/browse/RFPL-987?page=com.atlassian.jira.plugin.s... ] Ilya Shaikovsky commented on RFPL-987: -------------------------------------- sean please make some minor corrections and let's resolve that task. All the details should be added in separate improvement tasks. 1) in overview change The <a4j:push> component uses the Comet model for pushing data to the client. to We integrate with the Atmosphere framework which provides various transport mechanisms according to concrete browser support(Comet, HTML5 WebSockets). 2) basic usage RichFaces *Push using* jquery-atmosphere.js client plug-in for push functionality. *It's added by the component renderer.* Add the server-side Atmosphere framework *should be added* as a build dependency to your project. 3) console guide link -> http://docs.jboss.org/jbossas/6/Admin_Console_Guide/en-US/html/ 4) 3.8.2. Handling a push notification clarify with the note about two ways of handling the events.. something like: "dataavailable event could be processed using attached behavior as in Example 3.6. Basic usage, or by just plain JavaScript to perform pure client side updates as shown below in Example 3.7. Handling a push notification *using JavaScript*" General additions has to be done (pick the info from there http://in.relation.to/Bloggers/Ilya): 1) Web Application Configuration - must be described. prefer to see right after JMS config. 2) TopicsContext initialization - also a must. That initialization actually connecting our Push topics to JMS topics. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira