It depends what you mean. Seam Remoting has a nice API for pushing messages to the client via a JMS topic. But currently this is implemented on top of standard servlet spec mechanisms which use blocking IO. The reason why the next generation of servlet engines is offering special support for "comet" is that they can provide an implementation based upon NIO. When this stuff is actually productized into Tomcat and/or standardized in the servlet spec, Seam remoting can use that as the underlying implementation. Currently what is in todays servlet engines is highly experimental. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027349#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...