This is now complete.
As one of our community members has reported, Tomcat 7 trunk passes the
WebSocket 1.0 TCK with NIO.
I have also tested BIO, NIO and APR/native with Autobahn and all three
pass. I've added that (and a test I ran for 8.0.x at the same time) to
the Autobahn results on
On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas ma...@apache.org wrote:
Investigating some Gump and BuildBot failures has identified a large
block of functionality that still remains to be back-ported to 7.0.x -
namely the changes to Coyote that allowed upgraded connections to
support concurrent
On 22/08/2013 15:30, Niki Dokovski wrote:
On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas ma...@apache.org wrote:
Investigating some Gump and BuildBot failures has identified a large
block of functionality that still remains to be back-ported to 7.0.x -
namely the changes to Coyote that allowed
On Thu, Aug 22, 2013 at 5:47 PM, Mark Thomas ma...@apache.org wrote:
On 22/08/2013 15:30, Niki Dokovski wrote:
On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas ma...@apache.org wrote:
Investigating some Gump and BuildBot failures has identified a large
block of functionality that still
On 22/08/2013 16:06, Niki Dokovski wrote:
On Thu, Aug 22, 2013 at 5:47 PM, Mark Thomas ma...@apache.org wrote:
On 22/08/2013 15:30, Niki Dokovski wrote:
On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas ma...@apache.org wrote:
Investigating some Gump and BuildBot failures has identified a large
Investigating some Gump and BuildBot failures has identified a large
block of functionality that still remains to be back-ported to 7.0.x -
namely the changes to Coyote that allowed upgraded connections to
support concurrent read and write.
It isn't as simple as copy and paste as there has been
On 20/08/2013 06:35, Rainer Jung wrote:
On 19.08.2013 15:22, Mark Thomas wrote:
I plan to commit what I have so far once I am happy that the unit tests
still work.
I do want to look at removing the Java 7 dependency from the WebSocket
implementation - at least for Tomcat 7 - but I don't
On 16/08/2013 15:46, Mark Thomas wrote:
The JSR-356 API and implementation has been back-ported to Tomcat 7.
The necessary plumbing for the non-blocking support required by JSR-356
has been back-ported to Tomcat 7.
All compilation errors have been resolved.
The unit tests all pass.
On 08/19/2013 03:22 PM, Mark Thomas wrote:
I plan to commit what I have so far once I am happy that the unit tests
still work.
Cool
Jean-Frederic
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional
On 19.08.2013 15:22, Mark Thomas wrote:
On 16/08/2013 15:46, Mark Thomas wrote:
Updating the build script has proved interesting. The WebSocket
implementation depends on Tomcat internals but was also required to
build the examples. That meant that the WebSocket build script was
significantly
The JSR-356 API and implementation has been back-ported to Tomcat 7.
The necessary plumbing for the non-blocking support required by JSR-356
has been back-ported to Tomcat 7.
All compilation errors have been resolved.
The unit tests all pass.
Still to do:
1. Remove any Java 7 features so the
11 matches
Mail list logo
