Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Mark Thomas
On 16/08/2013 14:38, Rossen Stoyanchev wrote: > On Thu, Aug 15, 2013 at 6:47 PM, Mark Thomas wrote: >> This isn't going to be quite as simple as I first thought. >> >> The WebSocket client API requires Java SE 7 or later. >> The WebSocket server API requires Java EE 6 or later. >> Java EE 6 requir

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Rossen Stoyanchev
On Thu, Aug 15, 2013 at 6:47 PM, Mark Thomas wrote: > This isn't going to be quite as simple as I first thought. > > The WebSocket client API requires Java SE 7 or later. > The WebSocket server API requires Java EE 6 or later. > Java EE 6 requires Java 6 or later. > The WebSocket server API depend

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Niki Dokovski
On Fri, Aug 16, 2013 at 11:01 AM, Mark Thomas wrote: > On 16/08/2013 08:16, Niki Dokovski wrote: > > On Fri, Aug 16, 2013 at 9:54 AM, Mark Thomas wrote: > > > >> Christopher Schultz wrote: > >>> Mark, > >>> > >>> On 8/15/13 6:47 PM, Mark Thomas wrote: > This isn't going to be quite as simp

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Mark Thomas
On 16/08/2013 08:16, Niki Dokovski wrote: > On Fri, Aug 16, 2013 at 9:54 AM, Mark Thomas wrote: > >> Christopher Schultz wrote: >>> Mark, >>> >>> On 8/15/13 6:47 PM, Mark Thomas wrote: This isn't going to be quite as simple as I first thought. The WebSocket client API requires Jav

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Mark Thomas
Nick Williams wrote: > >On Aug 15, 2013, at 5:47 PM, Mark Thomas wrote: >> My (untested) plan is as follows: >> - Create a WebSocket module >> - Back-port (i.e. copy) the trunk code to that module >> - Build just that module with Java 7 >> - Make the minimum changes necessary to get it to work >>

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-16 Thread Niki Dokovski
On Fri, Aug 16, 2013 at 9:54 AM, Mark Thomas wrote: > Christopher Schultz wrote: > >Mark, > > > >On 8/15/13 6:47 PM, Mark Thomas wrote: > >> This isn't going to be quite as simple as I first thought. > >> > >> The WebSocket client API requires Java SE 7 or later. > >> The WebSocket server API re

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-15 Thread Mark Thomas
Christopher Schultz wrote: >Mark, > >On 8/15/13 6:47 PM, Mark Thomas wrote: >> This isn't going to be quite as simple as I first thought. >> >> The WebSocket client API requires Java SE 7 or later. >> The WebSocket server API requires Java EE 6 or later. >> Java EE 6 requires Java 6 or later. > >

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-15 Thread Niki Dokovski
On Fri, Aug 16, 2013 at 4:34 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > Mark, > > On 8/15/13 6:47 PM, Mark Thomas wrote: > > This isn't going to be quite as simple as I first thought. > > > > The WebSocket client API requires Java SE 7 or later. > > The WebSocket server API r

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-15 Thread Christopher Schultz
Mark, On 8/15/13 6:47 PM, Mark Thomas wrote: > This isn't going to be quite as simple as I first thought. > > The WebSocket client API requires Java SE 7 or later. > The WebSocket server API requires Java EE 6 or later. > Java EE 6 requires Java 6 or later. Clarification: are you saying that Jav

Re: Back-porting JSR-356 implementation to 7.0.x

2013-08-15 Thread Nick Williams
On Aug 15, 2013, at 5:47 PM, Mark Thomas wrote: > This isn't going to be quite as simple as I first thought. > > The WebSocket client API requires Java SE 7 or later. > The WebSocket server API requires Java EE 6 or later. > Java EE 6 requires Java 6 or later. > The WebSocket server API depends