search

javaee / grizzly

Writing scalable server applications in the Java™ programming language has always been difficult. Before the advent of the Java New I/O API (NIO), thread management issues made it impossible for a server to scale to thousands of users. The Grizzly NIO framework has been designed to help developers to take advantage of the Java™ NIO API.
https://javaee.github.io/grizzly/
Other
221 stars 60 forks source link

Handling incorrect cometd message sequence #263

Closed glassfishrobot closed 14 years ago

glassfishrobot commented 16 years ago

We need a better handling of incorrect / inappropriate cometd message sequence. For instance, if we send an array of messages as follows: (1) connect (2) publish (3) publish (4) connect The last connect seems to be redundant. We need to handle this correctly, for instance, in resuming cometd handler.

Environment

Operating System: All Platform: All

Affected Versions

[1.9.22]

glassfishrobot commented 16 years ago

Reported by swchan2@java.net

glassfishrobot commented 16 years ago

jfarcand@java.net said: Fix target.

glassfishrobot commented 16 years ago

jfarcand@java.net said: Re-assign

glassfishrobot commented 15 years ago

jfarcand@java.net said: Next release...

glassfishrobot commented 15 years ago

jfarcand@java.net said: Fix target

glassfishrobot commented 15 years ago

swchan2@java.net said: see fixes in issue 334

glassfishrobot commented 15 years ago

jfarcand@java.net said: Fix target

glassfishrobot commented 16 years ago

Was assigned to swchan2@java.net

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA GRIZZLY-263

glassfishrobot commented 14 years ago

Marked as fixed on Wednesday, December 16th 2009, 6:13:23 pm