Push component itself is very important for interactive enterprise applications and we are trying to design its API as much clean as possible.
RichFaces team, and Nick Belaevski namely, did great job to decouple Push from JMS to avoid unnecessary overhead with connecting to messaging provider.
On the client-side, changes have been done to support WebSockets as light-weight alternative for long-polling HTTP connections (comet). Clients, which supports them, uses WebSockets by default and fall-backs to long-polling when support is not detected.
Specifically for 4.0.0.Final users, which would like to try M1 release, they may register message stating deprecation of PushFilter in the server log. It is not strictly necessary to re-configure, but PushFilter has been replaced by PushServlet, to which it delegates now. Things are even better in Servlets 3.0 environments, when you don’t need register any servlet since that will be done automatically for you.
On the server-side, we have introduced option for disabling Push and JMS integration in cases when you can’t use enterprise messaging or you don't require it. To turn JMS integration off, you just need to provide following contextual parameter in web.xml:
<context-param>
<param-name>org.richfaces.push.jms.disable</param-name>
<param-value>true</param-value>
</context-param>
If you would like to try Push, you may be pleased that it is now in RichFaces Showcase, however be aware that it can't be seen in demo hosted on GAE since this hosting doesn't support JMS. You will need to deploy it at own, and in such case I strongly recommend you my previous blog.
And what you may expect in near future? We are working on integration with CDI Events feature, so your application would be allowed to throw messages to the clients very easily. This feature can be already seen in RichFaces Showcase Push samples - it is not really hard to develop simple integration with CDI.
But there were also issues which we had to overcome - one of them is issue with Atmosphere and JBoss Web which will be addressed also in M2.
To overcome this issue, you can temporary switch to using blocking I/O approach:
<context-param>
<param-name>org.atmosphere.useBlocking</param-name>
<param-value>true</param-value>
</context-param>
And off-course, if you have ideas how to make Push more user-friendly than it already is, give us know in RichFaces community discussions. We will be pleased to hear from you!
Posts
