Joakim Erdfelt 8dba440317 Issue #3279 - WebSocket Close Refactoring ... + FrameFlusher "close" frames are detected during enqueue and sets the state properly for failing other frames after it + Moving away from Blockhead(Client|Server) to using actual implementations + Moved tests to /jetty-websocket-tests/ to be able to use actual impl for both sides of testcase (client and server) + Corrected FrameFlusher terminate/close to not fail the close frame itself, but only frames that arrive AFTER the close frame. + Moving WebSocketCloseTest to jetty-websocket-tests to avoid using BlockheadClient / BlockheadServer in testing + Cleanup of unnecessary modifiers on interface + Logging error if @OnWebSocketError is undeclared + IOState removed + New ConnectionState tracks connection basics in a simpler method then IOState did. + No tracking of Remote close initiated (not needed) + IncomingFrames.incomingError() removed + Session delegates to Connection for all state changes + Errors can be communicated to application multiple times + Close is only communicated once Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>		2019-02-15 10:07:24 -05:00
..
src/test	Issue #3279 - WebSocket Close Refactoring	2019-02-15 10:07:24 -05:00
pom.xml	Updating to version 9.4.15-SNAPSHOT	2018-11-14 16:42:40 -06:00