Re: Back-porting JSR-356 Progress update

2013-08-23 Thread Mark Thomas
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 people.a.

Re: Back-porting JSR-356 Progress update

2013-08-22 Thread Mark Thomas
On 22/08/2013 16:06, Niki Dokovski wrote: > On Thu, Aug 22, 2013 at 5:47 PM, Mark Thomas wrote: > >> On 22/08/2013 15:30, Niki Dokovski wrote: >>> On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas wrote: >>> Investigating some Gump and BuildBot failures has identified a large block of funct

Re: Back-porting JSR-356 Progress update

2013-08-22 Thread Niki Dokovski
On Thu, Aug 22, 2013 at 5:47 PM, Mark Thomas wrote: > On 22/08/2013 15:30, Niki Dokovski wrote: > > On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas wrote: > > > >> Investigating some Gump and BuildBot failures has identified a large > >> block of functionality that still remains to be back-ported t

Re: Back-porting JSR-356 Progress update

2013-08-22 Thread Mark Thomas
On 22/08/2013 15:30, Niki Dokovski wrote: > On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas 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

Re: Back-porting JSR-356 Progress update

2013-08-22 Thread Niki Dokovski
On Thu, Aug 22, 2013 at 1:08 AM, Mark Thomas 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 read and wri

Re: Back-porting JSR-356 Progress update

2013-08-21 Thread Mark Thomas
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 so

Re: Back-porting JSR-356 Progress update

2013-08-20 Thread Mark Thomas
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

Re: Back-porting JSR-356 Progress update

2013-08-19 Thread Rainer Jung
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 > signifi

Re: Back-porting JSR-356 Progress update

2013-08-19 Thread jean-frederic clere
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 comm

Re: Back-porting JSR-356 Progress update

2013-08-19 Thread Mark Thomas
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 pas