Ajax Action
a4j:ajax
a4j:commandButton
a4j:commandLink
a4j:actionListener
a4j:jsFunction
a4j:poll
a4j:push
a4j:param
Ajax Queue
a4j:queue
a4j:attachQueue
Ajax Output/Containers
a4j:outputPanel
a4j:status
a4j:region
a4j:mediaOutput
a4j:log
Validation
Client Side Validation
rich:graphValidator
rich:message
rich:messages
rich:notify
Data Iteration
a4j:repeat
rich:dataTable
rich:extendedDataTable
rich:collapsibleSubTable
rich:dataScroller
rich:list
rich:dataGrid
Trees
rich:tree
Tree Adaptors
Output/Panels
rich:panel
rich:togglePanel
rich:tabPanel
rich:collapsiblePanel
rich:accordion
rich:popupPanel
rich:progressBar
rich:tooltip
Menus
rich:panelMenu
rich:toolbar
rich:contextMenu
rich:dropDownMenu
Inputs
rich:autocomplete
rich:calendar
rich:editor
rich:inputNumberSlider
rich:inputNumberSpinner
rich:inplaceInput
rich:fileUpload
Selects
rich:inplaceSelect
rich:select
rich:orderingList
rich:pickList
Drag and Drop
Drag and Drop
Miscellaneous
Standard elements skinning
Placeholder
RichFaces functions
Focus
rich:componentControl
rich:hashParam
rich:hotKey
rich:jQuery

Push can be controlled by a programmatic API. However a durable topic still needs to be created and registered in both RichFaces and the Java Messaging Service.

ba800880-2c7a-4d19-aaa1-20aa905f06eb

The programmatic API consists of a TopicKey which addresses the topic, and a TopicsContext which is used for publishing messages.

For the purpose of observing events from the server, the client creates a permanent connection to the server either by using a WebSocket connection or the long-polling method. Permanent connections are managed by the Atmosphere Framework.

In this example, the message doesn't contain any data - it instructs the client to re-render part of the page. In this case it forces the client to load new unique ID.