738cbfdccc
refactored client to use upgradeable endpoint. Instert SslConnection when needed
2011-10-27 16:37:07 +11:00
61664d3c0f
Added concept of SslConnection
2011-10-26 01:15:59 +11:00
5140a95144
refactored HttpConnection name
2011-10-20 15:12:19 +11:00
0e284f78f5
Protected HttpParser from multiple entry.
2011-10-20 12:18:10 +11:00
49f8b0de1a
Websocket partially refactored and passing tests
2011-10-18 21:59:49 +11:00
6edb7c1930
organised imports
2011-10-18 15:05:22 +11:00
e43b718fb1
Refactored NIO to better handle half closes. Applied the following policy:
...
Call shutdownOutput to signal the other end that you have written all the data that your are going to write (eg and the end of a non persistent HTTP response). This can be done either by generator (when it is complete) or coordinator or handle - but we need to decide which and have only 1 doing it.
Call shutdownInput to signal your own end that you have read -1 and to allow other local code to check that with an isInputShutdown. Ideally we could get by without any calls at all to shutdownInput, so long as we well handle reading -1 (Currently we don't). This should be done by whatever does the IO read.
Calling close should always be a real TCP close, even with SSL. SSL shutdown
The default handling of an idle callback should be close. But some connections (NOT endpoints) may implement idle as initiating a shutdown exchange (eg websocket close). If they do, this is state that should be held in the connection or parser - ie do-this-exhange-and-then-shutdown
Call close when you want to shutdown Output and you have already read -1, so input is already shutdown. We need to double verify that this is correct and that if a FIN has been received from the other end, that a close will not result in a reset. I'll do that today.
Call close when you want to shutdown Input and output has already been shutdown. This means you have read -1 after having sent a FIN.
Call close on any errors.
The current state is that server HttpConnection appears to be working well. Other connection types have not been updated and/or tested
2011-10-18 14:38:02 +11:00
7d10182034
[maven-release-plugin] prepare for next development iteration
2011-10-11 08:47:07 -05:00
b6ac542604
[maven-release-plugin] prepare release jetty-7.5.3.v20111011
2011-10-11 08:47:00 -05:00
0c55c774d4
[maven-release-plugin] prepare for next development iteration
2011-10-06 17:25:38 -05:00
4d822759de
[maven-release-plugin] prepare release jetty-7.5.2.v20111006
2011-10-06 17:25:32 -05:00
b58006b4a4
[maven-release-plugin] prepare for next development iteration
2011-10-06 09:43:37 -05:00
7eca345e8d
[maven-release-plugin] prepare release jetty-7.5.2.v20111006
2011-10-06 09:43:31 -05:00
c438d7c043
improved websocket testserver example to include ping/pong
2011-10-03 18:03:57 +11:00
fbb4893352
improved websocket testserver example to include ping/pong
2011-10-03 18:03:42 +11:00
7bf5f7792b
359673 updated websocket version handling
2011-10-03 16:04:37 +11:00
18aa8fed9b
359673 updated websocket version handling
2011-10-03 16:04:13 +11:00
a6988108c3
minor cleanups and extra debug
2011-09-16 15:29:28 +10:00
54961fca1f
refined test options and output
2011-09-14 14:17:09 +10:00
55d229e73c
357338 remove debug
2011-09-13 00:38:08 +10:00
c5e6378b84
357338 Improve UTF-8 validation
2011-09-12 13:14:09 +10:00
4c885ca3ad
357178 websockets draft 14 support
2011-09-09 12:10:01 +10:00
ebdb89dc23
[maven-release-plugin] prepare for next development iteration
2011-09-08 12:00:16 -05:00
932245a114
[maven-release-plugin] prepare release jetty-7.5.1.v20110908
2011-09-08 12:00:10 -05:00
37d0f53b0a
updating version.txt and resetting pom versions to 7.5.1-SNAPSHOT
2011-09-08 11:40:37 -05:00
4a575d4958
Merge branch 'master' into release
2011-09-08 11:36:48 -05:00
e914e0f97f
improved websocket handling of error cases for autobahn test suite
2011-09-09 01:52:27 +10:00
b8556bec76
fixes from running autobahn test suite
2011-09-08 11:35:39 +10:00
6b614a54f0
[maven-release-plugin] prepare for next development iteration
2011-09-07 18:12:16 -05:00
ce55c8c601
[maven-release-plugin] prepare release jetty-7.5.1.v20110907
2011-09-07 18:12:09 -05:00
1744b5bce1
reset from release
2011-09-07 11:09:46 -05:00
ae86ad6d4e
[maven-release-plugin] prepare for next development iteration
2011-09-07 10:03:16 -05:00
86383afbd2
[maven-release-plugin] prepare release jetty-7.5.1.v20110907
2011-09-07 10:03:10 -05:00
65a1e84886
misc findbugs cleanups
2011-09-07 15:57:18 +10:00
cf45e7b647
356823 correctly decode close codes. Send not utf-8 close code.
2011-09-07 11:37:46 +10:00
1d6079e78f
findbugs inspired code cleanups
2011-09-06 11:22:37 +10:00
b1f95541de
Fixes #356749 (WebSocket message length is computed wrongly when greater than 0xFFFF), and a bunch of other silly mistakes.
2011-09-06 00:18:02 +02:00
a8ce6e8878
Fixed pom.xml by declaring dependencies in the right way.
...
Dependency on jetty-server must be kept with scope provided (the classes that depend on jetty-server can only be run on Jetty).
2011-09-05 11:18:47 +02:00
8a40a0d9fb
356695 jetty server jars are provided for websockets
2011-09-05 11:21:26 +10:00
a728021edf
[maven-release-plugin] prepare for next development iteration
2011-09-01 11:17:05 -05:00
882308f781
[maven-release-plugin] prepare release jetty-7.5.0.c20110901
2011-09-01 11:16:58 -05:00
c3e170bb74
Merge branch 'master' into release
2011-09-01 10:56:08 -05:00
6a15cf7dc7
javadoc
2011-09-01 23:49:30 +10:00
e68d056b0f
setters for max message size in client factory
2011-09-01 23:33:05 +10:00
0b489b8877
356421 Upgraded websocket to draft 13 support
2011-09-01 12:11:10 +10:00
9528870b23
improved setting of default message maximums
2011-09-01 10:48:43 +10:00
57e9045635
[maven-release-plugin] prepare for next development iteration
2011-08-31 14:17:32 -05:00
317491a4d7
[maven-release-plugin] prepare release jetty-7.5.0.v20110901
2011-08-31 14:17:25 -05:00
0f8939dd96
Added test for the lost messages bug.
2011-08-31 18:29:09 +02:00
ba87334389
353073 better warnings
2011-08-31 21:53:34 +10:00
Greg Wilkins
Jesse McConnell
Simone Bordet