Handling incorrect cometd message sequence

ari-ban / issue-test

0 stars 0 forks source link

Handling incorrect cometd message sequence #263

Closed arinban closed 14 years ago

arinban 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]

arinban commented 6 years ago

Issue Imported From: https://github.com/javaee/grizzly/issues/263
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To:@glassfishrobot
Original Issue Closed By:@glassfishrobot

arinban commented 16 years ago

@glassfishrobot Commented Reported by swchan2@java.net

arinban commented 16 years ago

@glassfishrobot Commented jfarcand@java.net said: Fix target.

arinban commented 16 years ago

@glassfishrobot Commented jfarcand@java.net said: Re-assign

arinban commented 15 years ago

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

arinban commented 15 years ago

@glassfishrobot Commented jfarcand@java.net said: Fix target

arinban commented 15 years ago

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

arinban commented 15 years ago

@glassfishrobot Commented jfarcand@java.net said: Fix target

arinban commented 16 years ago

@glassfishrobot Commented Was assigned to swchan2@java.net

arinban commented 7 years ago

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

arinban commented 14 years ago

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