-
Hi,
I just see a NullPointerException in DataHandler.java.
The following is my proposal fix:
/export/grizzly/src/trunk/modules/cometd/src/main/java/com/sun/grizzly/cometd >
svn diff DataHandler.java
…
-
There are inconsistencies with the way Grizzly handles connect requests without
handshakes. I can send in a successful connect request with any client id but
Jetty responds with an error "invalid clie…
-
In current implementation of BayeuxClient.java in extras/cometd-client.
We do a reconnect even after _disconnecting = false.
This will force BayeuxClient to send a connect message even after a disconn…
-
When an web application fail to deploy because all its dependencies aren't
available, the application is considered to be deployed even if the deployment
has failed. Attached is an example. The applic…
-
During the porting of Jetty Java Bayeux client this error was encountered. Jetty
client sends messages of content type text/json by default. Grizzly doesn't like
this but still it responds with a 200 …
-
Any channel requested by the users must be represented by a CometContext. Right
now we are filtering using a NotificationHandler, and this is not appropriate.
#### Environment
Operating System: All
Pl…
-
Right now we aren't allowing pushing data to unsubscribed channel but it seems
the spec mandate that (that is really bad if that's true!). Still a useful
feature so make it configurable via
-Dcom.sun…
-
I don't know exactly how to trigger this but Grizzly sometimes replies with a
malformed response like this:
Request(has been URL decoded):
message=
{"channel":"/meta/connect","clientId":"24a3f2867fa…
-
Currentlty, all module have the following pattern in their package:
src/main/java/com/sun/grizzly/standalone//Main.java
Those Main.java classes (liked Comet.java, Cometd.java) should be moves from
m…
-
The current DataHandler hardcode the "NOTIFY_END" final message used to resume
the response. When the JavaAPI is used, it is impossible to know that we need to
push the NOTIFY_END event without lookin…