Java.net JIRA

[ATMOSPHERE-107] Problems with Atmosphere GWT and Antivirus (Avast in this case)

Fri, 10 Jun 2011 01:32:32 +0000 (GMT+00:00)

Connections to the server with localhost clients or without any antivirus WEB protection, results in a correct behaviour, where messages notifications and client/server interations were done succesfully.
Activating antivirus (or generally in a production environment), the comunication from client/server hangs, and asynch notification functionallities cease to work.
We have seen that this is a well-known problem. With previuos libraries release (0.6.5), we solved overriding service method of AtmosphereGWTServlet and set:

response.setHeader("Server", "DWR-Reverse-Ajax");

but this workaround doesn't work in 0.7. We also try with:

response.setContentType("text/html");
response.setHeader("X-Content-Type-Options", "nosniff");

without success.

Into attached logfile.txt you could see the result of a connection made from an intranet client (client and server are into the same net subring) with Avast WEB protection active. We also tried to activate Comet valve for Tomcat (and add libraries), but nothing change.
No problems with test made with same intranet client without antivirus or WEB protection disabled.

[ATMOSPHERE-158] GWT client implementation and style OBF

Thu, 18 Aug 2011 09:37:21 +0000 (GMT+00:00)

In BaseCometTransport.getUrl method class names of transport classes extracted and send later via. a get parameter to the atmosphere servlet. This seams to me not working in the OBF compiler mode. So is gwt client implementation of atmosphere incompatible with obfuscated gwt mode?

[ATMOSPHERE-154] BroadcasterConfig should not use a unbounded thread pool for async writes as default

Mon, 8 Aug 2011 22:00:01 +0000 (GMT+00:00)

See BroadcasterConfig#configExecutors.

As Paul Tyma put it: "Executors.newCacheThreadPool evil, die die die" (http://www.mailinator.com/tymaPaulMultithreaded.pdf).

Instead, it should use a fixed thread pool with a configurable number of threads as default.

[ATMOSPHERE-151] 2 tests failed on Windows7

Thu, 28 Jul 2011 02:43:36 +0000 (GMT+00:00)

Results :

Failed tests:
testConcurrentBroadcast(org.atmosphere.tests.GrizzlyCometSupportTest)
testConcurrentBroadcast(org.atmosphere.tests.Jetty6CometSupportTest)

Tests run: 84, Failures: 2, Errors: 0, Skipped: 0

[ATMOSPHERE-150] Concurrency InterruptedException on suspend(period) with pooling

Wed, 27 Jul 2011 17:32:05 +0000 (GMT+00:00)

Let's start with the exception and talk about the context after.

ERROR [DefaultBroadcaster] - failed to submit broadcast handler runnable to broadcast executor service on shutdown
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:1899)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1934)
at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
at org.atmosphere.cpr.DefaultBroadcaster$2.run(DefaultBroadcaster.java:352)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Ok.. to create this it's simple. Create a AtmosphereServlet and set no BroadcasterCache and do a get with suspend(period)

The connection will suspend until there is a message, but because there isn't cache, when the client connect, it won't send message to this client, so it waits.

When the suspend expired, DefaultBroadcaster.destroy() it's called.

and DefaultBroadcasterFactory.destroy() will be also called.

and it's in this function that the error will occur

DefaultBroadcasterFactory
/**

{@inheritDoc}
*/
public void destroy()
Unknown macro: { Enumeration<Broadcaster> e = store.elements(); while (e.hasMoreElements()) { e.nextElement().destroy(); //HERE.. } store.clear(); factory = null; }

I created a usecase USE BasePubSubTest and change this :

@BeforeMethod(alwaysRun = true)
public void setUpGlobal() throws Exception { port = TestHelper.getEnvVariable("ATMOSPHERE_HTTP_PORT", findFreePort()); urlTarget = getUrlTarget(port); atmoServlet = new AtmosphereServlet(); atmoServlet.addInitParameter("com.sun.jersey.config.property.packages", this.getClass().getPackage().getName()); //atmoServlet.addInitParameter("org.atmosphere.cpr.broadcasterClass", RecyclableBroadcaster.class.getName()); configureCometSupport(); startServer(); }

@Test (timeOut = 15000)
public void testHeaderBroadcasterCache() throws IllegalAccessException, ClassNotFoundException, InstantiationException {
logger.info("{}: running test: testHeaderBroadcasterCache", getClass().getSimpleName());

//atmoServlet.setBroadcasterCacheClassName(HeaderBroadcasterCache.class.getName());
....

and in PUBSUBTEST

I added the period.

/**

Suspend the response, and tell teh framework to resume the response
when the first @Broadcast operation occurs.
@return A {@link org.atmosphere.jersey.Broadcastable} used to broadcast events.
*/
@GET
@Suspend(resumeOnBroadcast=true, outputComments = false, period=5000)
@Path("subscribeAndResume")
public Broadcastable subscribeAndResume() { return new Broadcastable(broadcaster); }

[ATMOSPHERE-148] Seeing "This Broadcaster has been destroyed and cannot be used" error with EMPTY_DESTROY policy

Wed, 27 Jul 2011 01:02:58 +0000 (GMT+00:00)

When using the EMPTY_DESTROY policy, I see this error in the logs every once in a while:

WARN 2011-07-27 00:14:36,179 21250486@qtp-18623335-86 org.atmosphere.cpr.DefaultBroadcasterFactory This Broadcaster has been destroyed and cannot be used
java.lang.IllegalStateException: This Broadcaster has been destroyed and cannot be used
at org.atmosphere.cpr.DefaultBroadcaster.removeAtmosphereResource(DefaultBroadcaster.java:741)
at org.atmosphere.cpr.DefaultBroadcasterFactory.removeAllAtmosphereResource(DefaultBroadcasterFactory.java:204)
at org.atmosphere.cpr.AsynchronousProcessor.destroyResource(AsynchronousProcessor.java:377)
at org.atmosphere.cpr.AsynchronousProcessor.invokeAtmosphereHandler(AsynchronousProcessor.java:368)
at org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:331)
at org.atmosphere.container.JettyCometSupport.service(JettyCometSupport.java:99)
at org.atmosphere.cpr.AtmosphereServlet.doCometSupport(AtmosphereServlet.java:1156)
at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:1138)
at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:1124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:398)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:525)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

[ATMOSPHERE-147] resource is not available after a resume

Wed, 20 Jul 2011 18:55:59 +0000 (GMT+00:00)

I have Struts1 or Struts2 with Meteor to suspend a request. The code is this

public class OpenChannelAction extends Action {
public static final Logger logger = Logger.getLogger(OpenChannelAction.class);
private final List<BroadcastFilter> list;
private final Broadcaster b = new DefaultBroadcaster("Struts");

public OpenChannelAction() { list = new LinkedList<BroadcastFilter>(); }

@Override
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws Exception { logger.info("BEGIN OpenChannelAction"); final Meteor m = Meteor.build(request, list, null); request.getSession().setAttribute("meteor", m); m.suspend(3000); return mapping.findForward("success"); }

}

the request will resume after 3 sec.

The problem is that the resource return by mapping.findForward("success"); Doesn't return a static web page.

Let suppose the basic case.. it will forward to a .html. if it's the case.. BRAVO it works. but if you forward to a JSP, it will return the content of the JSP, but if you return a action. it will failed with a message :

The requested resource (/AtmoStruts2Demo/viewList) is not available

I expect that Atmosphere is able to handle that case.

here a plain basic forward action .

to test.. just compile the attachment and run this URL

http://localhost:8080/AtmoStruts2Demo/index3.html and click on CONNECT

look into the console (firebug).. it will print the message after 3 sec.

[ATMOSPHERE-144] Implement new Websocket handling

Mon, 11 Jul 2011 07:24:57 +0000 (GMT+00:00)

See : http://is.gd/MiWLzE

[ATMOSPHERE-142] Support for Guice in Meteor

Wed, 6 Jul 2011 15:07:54 +0000 (GMT+00:00)

We need to support Guice injection for Meteor.

I'll provide a sample to start. I think it's a good example, because it Using Struts2. It's special because in Struts2 it's using filters and not servlet to handle request.

With the sample, we can call action, but not able to forward to .jsp. That need to be fixed too.

The first URL to test it this : http://localhost:8080/AtmoStruts2Guice/viewLogin.action

and for the streaming : http://localhost:8080/AtmoStruts2Guice/ajax/ajaxMeteor.action

when the JSP support will works, to complete the sample, we need to Inject a basic model in ViewLoginAction.java to test that the guice injection works.

thanks

[ATMOSPHERE-141] Add support for post-serialization filters

Mon, 4 Jul 2011 03:06:46 +0000 (GMT+00:00)

Please add support for post-serialization filters. Currently filters are executed BEFORE any form of serialization. This poses a problem for the JavascriptClientFilter, which is necessary to make comet calls work in IE8 and Opera. The filter adds some JavaScript to the responses that are pushed down to clients. However, the expects the messages to be of type String and thus it won't be executed when I broadcast ordinary Java objects that I want to serialize using the org.atmosphere.cpr.Serializer interface.

See the following forum entry for reference: http://atmosphere-users-mailling-list.2493822.n2.nabble.com/Filters-executed-before-Serializers-Problem-with-JavascriptClientFilter-when-using-Serializers-td6538155.html

[ATMOSPHERE-138] Improve Logging when encountering "Broken pipes"

Fri, 1 Jul 2011 15:42:40 +0000 (GMT+00:00)

As discussed on the mailing list:

http://atmosphere-users-mailling-list.2493822.n2.nabble.com/Handling-quot-Broken-Pipe-quot-SocketExceptions-nicer-td6531579.html

When clients "browse away" from websocket/comet connections, the server may encounter

"Caused by: java.net.SocketException: Broken pipe " etc. Basically, Atmosphere logs those stacktraces to the console.

It may be a good idea to either allow users to catch those exceptions themselves more easily, or at to least to give the user the configuration choice to have long (compete) or short (1 line) logging output in case this these exceptions occur.

As this issue can somewhat be mitigated by using the maxInactiveActivity paramter in web.xml:

<init-param>
<param-name>org.atmosphere.cpr.CometSupport.maxInactiveActivity</param-name>
<param-value>30</param-value>
</init-param>

Thus, maybe adding some descriptive content to the log message, explaining how to fix that using the property.

[ATMOSPHERE-132] Atmosphere not closing inactive connections (maxInactiveActivity)

Tue, 14 Jun 2011 06:14:15 +0000 (GMT+00:00)

With atmosphere 0.7.2, my inactive connections are not being closed when max inactive activity is reached.

Im using jboss6, APR native connector.

[ATMOSPHERE-129] Minimum packet size for google chrome

Fri, 10 Jun 2011 09:32:41 +0000 (GMT+00:00)

This is not necessarily a bug in Atmosphere but we may be able to find a way to deal with it. Chrome appears to have a minimum receive buffer size for comet implementations. It seems to be that a message sent from the server to Chrome will be ignored until at least 8 bytes of data are received. Padding the message with extra bytes works well.

A possible Atmosphere workaround could be that atmosphere detects a chrome browser and pads the message for us and perhaps adds some information in the header about the padding so the client implementation can strip it off. This would only work if it is possible to send header information mid-stream which I don't think is possible. Even if adding to the header isn't possible, automatically padding the message with spaces would probably be the least painful solution since most applications would trim off extra space anyway. I think ensuring all messages are a minimum of 8 characters (or whatever the minimum message size for chrome is) by padding with spaces is probably our best bet for sure. We should also to only add as much padding as we need to conserve bandwidth.

[ATMOSPHERE-127] DefaultBroadcasterFactory.getDefault().get() doesn't return the proper value for other module than atmosphere runtime

Wed, 8 Jun 2011 09:04:42 +0000 (GMT+00:00)

DefaultBroadcasterFactory.getDefault().get() doesn't return the proper value for other module than atmosphere runtime

[ATMOSPHERE-126] Conent-type "applicaiton/comet" and IE streaming

Wed, 8 Jun 2011 05:35:47 +0000 (GMT+00:00)

If the content-type in the Jersey resource is set to "application/comet" instead to "text/html" IE closes the streaming connection immediately after it was opened.

[ATMOSPHERE-118] Clean up Atmosphere's pom.xml

Fri, 20 May 2011 07:29:25 +0000 (GMT+00:00)

The current pom.xml is full of inconsistency and need to be cleaned up. Better dependencies management is required as well.

[ATMOSPHERE-116] Improve atmosphere jquery plugin to support message lenght definition: trackMessageSize

Tue, 14 Jun 2011 07:22:25 +0000 (GMT+00:00)

From Vincent Barrier

Disabled by default to enable it : $.atmosphere.request = {trackMessageSize:true}

Code has been tested on streaming and long-polling with and without junk code.

I also tried to simplify the js code :

auto check if junk code is send
always send the part of response we received

example : in long polling the whole message except junk code (better for json message)

Finally, there is a new var jQuery.atmosphere.junkSize, if you change the junk code don't forget to update this value

[ATMOSPHERE-114] The di-guice-sample does not work in IE

Thu, 5 May 2011 19:24:16 +0000 (GMT+00:00)

The di-guice-sample does not work in IE

[ATMOSPHERE-113] Broken link to GWT tutorial

Fri, 29 Apr 2011 13:02:10 +0000 (GMT+00:00)

http://atmosphere.java.net/ contains a broken link to "Getting started with GWT and Atmosphere".

[ATMOSPHERE-105] X-Cache-Date in jQuery plugin missing cached entries

Wed, 9 Mar 2011 09:28:02 +0000 (GMT+00:00)

X-Cache-Date as set on the client is getting out of sync with the entries in the header broadcaster cache on the server.

In jquery.atmosphere.js, the X-Cache-Date is always set to be the current time on the client. The entries that are being cached are using the time on the server. This can cause various different errors to occur:

In a long polling scenario where the "channel" is returning with entries, then reconnecting (at which time it gets anything that landed in the cache while it was gone) any entries made to the broadcaster cache between the response and the next request is actually not sent back to the client.

Also, what happens if the times on the client and server are themselves out of sync? If the client's clock is late, I assume the cache will never be used?

The fix would be to have the X-Cache-Date only set on the server.

The client makes the first request with X-Cache-Date=0, meaning it wants anything in the cache, or X-Cache-Date=client time, if it does not want history

++++ or maybe does not set the header at all on the first request if history is not desired? ++++

The server response sets the X-Cache-Date to the cache-date of the last cached element being returned in this response (if the cache is empty, it returns the current server time).

The client then has to use this time as returned from the server for its next request in order to get any elements that landed in the cache between the response and the next request.

CHANGES:
jquery.atmoshere.js uses the response X-Cache-Date in the next request
BroadcasterCacheBase.java sets system time for tail CachedMessage (is currently set to 0L)

[ATMOSPHERE-100] Use reflection to load the CometSupport container

Fri, 25 Feb 2011 08:17:38 +0000 (GMT+00:00)

Using reflection to load the CometSupport container will remove the dependencies on atmosphere.container.*. To be worked on for 0.8-SNAPSHOT.

Asked to be filed by Jeanfrancois.

[ATMOSPHERE-94] Collect missing jquery client features in atmosphere-gwt

Thu, 20 Jan 2011 05:27:37 +0000 (GMT+00:00)

Currently atmosphere-gwt is missing the following functionality available in the jquery client:

long polling

[ATMOSPHERE-88] Javascript client

Thu, 2 Jun 2011 13:00:35 +0000 (GMT+00:00)

Short description :
sources and targets of jQuery pubSub example containing new Javascript client and jQuery.atmosphere plugin. Contains netbeans project for comet connection applet.

=============================================================

Hi all,

Well that's it, the client is functional. I commented code the best I could.
This is a first shot so it is surely unperfect.

I have marked a lot of TODO within code for things to implement and options/adds to think about

Major things I have to say :

With employed connection strategy we can not guaranty a correct incoming HttpConnected state. This is the drawback of iframe streaming.

It would be possible to overcome it with an internal hello message protocol... but that's maybe not the purpose of our javascript client.

The major consequence is about connection events that are linked to this connected state : onConnect, onDisconnect, onReconnect. All we can let them mean is "we tryed to..." not "we have really...". On the contrary we can correctly detect when connection is lost. When we cannot establish HTTP connection we'll get this pattern : "onConnect then onConnectionLost" repeating as long as we keep trying reconnect.

I will certainly work again on message extraction implementation. It was not really my first focus. It is however functional... I hope

I've modifyed JavascriptFilter (of atmosphere-runtime) to allow JS callback function parameter being linked to suspended request on server side. I've named it RewroteJavascriptFilter.

I've wrote a simple Filter (SimpleMessageTestFilter) to test not using JavaScript events. To test it you need to modify web.xml, and set handler useJavascriptEventsMethod:false in index.html. Note : to get a perfect behavior, used Separator must be escaped within messages.

Right now I get trouble to use object that w3c recommends instead of deprecated applet (that is in fact more portable lol) will investigate... maybe that's cause I didnt signed jar but normally it should pass. There is actually no check if browser is applet capable : I will improve it later

For code I gave :

I exploded project into many files to ease development. We should compact these files into at least one prod version. I will let you do the repack. All stuff is in /webapp/atmosphere-client/ of jQueryPubSub sample.

Source of comet applet is in appletComet/ directory, this project depends of "plugin.jar" library cause of netscape.javascript.JSObject. It is a netbeans project that you'll surely easily repack to a maven one.

Well I guess that's all for now

[ATMOSPHERE-86] Non-servlet (stand-alone) API for Atmosphere

Tue, 4 Jan 2011 06:36:54 +0000 (GMT+00:00)

Wouldn't it be very useful to provide a thin layer on top of Atmosphere which hides the servlet interface? Perhaps a more complete spade-server like the following:

public static void main(String ... args){

//comet/websockets/whatever
AtmosphereServer server = new AtmosphereServer("localhost", 8080, "/chat", new AtmosphereServerHandler(){

public void onMessage(Message msg){ System.out.println(msg); }
public void onException(...){...}

});

server.broadcast("hello every one");
server.sendTo(specificClient, "hello specific client");
}

Very very simple interface, yet profoundly useful--just look at what people are doing with socket.io:
http://swarmation.com/
http://wargamez.mape.me/
http://projects.nuttnet.net/hummingbird/
and new ones every day

Java should be able to do this...without making programmers deal with servlets!

[ATMOSPHERE-83] DI support in Atmosphere

Tue, 7 Dec 2010 10:50:47 +0000 (GMT+00:00)

See Git Pull Request at

https://github.com/Atmosphere/atmosphere/pull/4

Contains:

API for adding DI support in Atmosphere (regardless of which DI framework)
An implementation module which implements this API for Guice
A sample application to demonstrate the injection is performed

Mathieu.

[ATMOSPHERE-75] Cannot dynamically add BroadcastFilter with Jersey if some defined in web.xml

Mon, 25 Oct 2010 10:21:58 +0000 (GMT+00:00)

Cannot dynamically add BroadcastFilter with Jersey if some defined in web.xml using

<param-name>org.atmosphere.cpr.broadcastFilterClasses</param-name>

AtmosphereFilter will not set any if the BroadcastConfig's already has filter.

[ATMOSPHERE-74] Unable to add Cluster's Filter via web.xml

Mon, 25 Oct 2010 10:20:01 +0000 (GMT+00:00)

Currently Filter defined in web.xml using

<param-name>org.atmosphere.cpr.broadcastFilterClasses</param-name>

[ATMOSPHERE-56] Allow Filters to be registered with any path

Tue, 21 Sep 2010 09:28:17 +0000 (GMT+00:00)

See

http://atmosphere-users-mailling-list.2493822.n2.nabble.com/Integration-with-Spring-existing-infrastructure-tt5456565.html#a5456565

[ATMOSPHERE-21] Twitter samples must be updated

Wed, 8 Sep 2010 06:49:34 +0000 (GMT+00:00)

The Twitter both samples must be updated. There is no API available, specially
for the Twitter sample constructed using atmosphere-jersey, which can be
significantly reduced in terms of code.

[ATMOSPHERE-8] Improve @Suspend Scope support

Wed, 8 Sep 2010 06:49:37 +0000 (GMT+00:00)

See:

http://n2.nabble.com/Tip-of-the-Friday--1---Broadcaster%27s-scope-tt3121388.html

[ATMOSPHERE-145] Provide release notes

Wed, 13 Jul 2011 13:37:48 +0000 (GMT+00:00)

It would easier to follow the change of the project if there were some release notes provided. Including the fixes added with the current releases and maybe the future changes that the next releases will bring. Could they be generated frome the jiras ?

[ATMOSPHERE-104] implement support for X-Cache-Date

Thu, 2 Jun 2011 13:01:38 +0000 (GMT+00:00)

Currently only the jquery client supports X-Cache-Date

[ATMOSPHERE-103] Different disconnect behaviour with and without WebSocket

Thu, 2 Jun 2011 13:03:34 +0000 (GMT+00:00)

With WebSocket, if I simply kill the server (with SIGINT) while a client is connected, the client listener will get onDisconnected events.

Without WebSocket, onError is called instead. It would be more consistent if the behaviour was the same in both cases.

On a related note, with WebSocket, onDisconnected seems to get called an infinite number of times in rapid succession unless I call AtmosphereClient.stop() explicitly. It would be nice if onDisconnected would only be called once.

[ATMOSPHERE-92] Broadcast to all but me method.

Tue, 11 Jan 2011 10:50:15 +0000 (GMT+00:00)

It would be nice to have a method in the Meteor class that broadcasts to all the Atmosphere resources but the one that is assigned with the meteor.

As a reference see:

http://atmosphere-dev-mailing-list.2493772.n2.nabble.com/Small-modifications-on-the-Meteor-class-td5910764.html

This will eventually require changes on the Broadcaster interface.

[ATMOSPHERE-91] twitter-rest sample popop error

Mon, 10 Jan 2011 15:19:15 +0000 (GMT+00:00)

there is a popop error

[ATMOSPHERE-87] JSon-based Notification-Framework

Fri, 7 Jan 2011 07:32:23 +0000 (GMT+00:00)

The idea is to have one single stream channel which initially does not listen to any notification.
If a client wants to listen to some certain notifications the client have to subscribe to each notification (type) manually.

Than notifications will be send over the one, single stream channel (if the client subscribed to certain notifications)
(this approach works good for heterogeneous service environments were also permissions must be checked).

I wrote a small, full working prototype to get a better explanation of my ideas.
Take a look at: https://code.google.com/p/atmosphere-notificationfw-prototype/

simply start atmosphere.notificationfw.prototype.Server
open http://localhost:8080/index.html in one (or more) browsers
take a look at webroot/index.html (a step-by-step example, which should explain the idea)
also take a look at atmosphere.notificationfw.prototype.application.Resource for server side functionalities