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

NOTIFY_END must not be hardcoded inside DataHandler #290

Closed glassfishrobot closed 14 years ago

glassfishrobot commented 16 years ago

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 looking at the code.

We should add a method on DeliverResponse that handle that case.

Environment

Operating System: All Platform: All

Affected Versions

[1.9.0]

glassfishrobot commented 16 years ago

Reported by jfarcand@java.net

glassfishrobot commented 16 years ago

jfarcand@java.net said: Sending cometd/src/main/java/com/sun/grizzly/cometd/DataHandler.java Sending cometd/src/main/java/com/sun/grizzly/cometd/bayeux/DeliverResponse.java Transmitting file data .. Committed revision 1683.

glassfishrobot commented 16 years ago

Was assigned to grizzly-issues

glassfishrobot commented 7 years ago

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

glassfishrobot commented 14 years ago

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