Re: [equinox-dev] Jetty version for Luna?

[Thomas Watson <tjwatson@xxxxxxxxxx>]

We are looking to move up the Jetty 9 for
Equinox.  But from the perspective of the http service impl in Equinox
it is expected to work across multiple container implementations and Servlet
specification levels.  Jetty 9 is attractive for several reasons as
you mentioned.  Another benefit is to make sure the http service works
on the latest spec release of Servlet.

WRT to plans.  The move to jetty
9 can happen at anytime, but need someone to step up to do the work.  Last
I checked we do have some initial work done in https://bugs.eclipse.org/bugs/show_bug.cgi?id=401784
but need someone to dust that one off and see if it is in shape to get
into Mars.  The R6 impl of Http Whiteboard specification is coming
along, but realistically it probably will not be ready until M4.

Tom





From:      
 Scott Lewis <slewis@xxxxxxxxxxxxx>
To:      
 equinox-dev@xxxxxxxxxxx
Date:      
 09/18/2014 11:27 AM
Subject:    
   Re: [equinox-dev]
Jetty version for Luna?
Sent by:    
   equinox-dev-bounces@xxxxxxxxxxx

---

With Ray's Auge's joining as an Equinox committer
(welcome Ray!) to 
apparently work at least partially on HttpService, and the changes wrt
this bug [1], and the fact that we are now on the Mars release cycle, I
would like to re-ask some planning questions

1) Is it reasonable to expect that Jetty 9 will be used for Equinox in
Mars (rather than Jetty 8)?
2) Does this interact at all with Ray's work on supporting OSGi R6 
HttpService specification?...i.e. is it reasonable to expect that R6 
HttpService will be supported in Equinox (by jetty9)?
3) Assuming 'yes' to one or both of above, are there any plans WRT 
timing of release for 1 or 2 (i.e. which Mars milestones)?

The primary reason these questions matter to me is that ECF's impl of 
OSGi R6 Remote Services allows for the use of multiple modular transport
providers, and we've been requested by the community (and have some 
contributions already) to use/depend upon websockets for a public RS 
provider [2].   Naturally we would like to reuse the Jetty impl of
websockets to implement this provider, and use the latest/most 
up-to-date websockets impl, which I assume is on the Jetty 9 stream.

As well, there is the potential that other RS/RSA users would like to 
use R6 HttpService to create their own RS providers, and this would be
vastly simplified if an R6-compliant HttpService impl was available via
EF/Equinox/Jetty.   We would like to make this as easy as possible
for 
RS/RSA consumers.

In any event, just wanted to open re-discussion some of these changes,
now that we are well into Mars cycle.

FWIW, I will offer some technical collaboration and support (e.g. at 
least testing in RS/RSA use cases for websockets and httpservice) for 
technical work implied above.   ECF's resources for new commitments
are 
limited, however, as many are probably aware.

Thanks,

Scott

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=401784

On 4/17/2014 2:44 PM, Scott Lewis wrote:
> Hi,
>
> I assume that since the current Equinox HttpService impl is provided
> by Jetty that some version of Jetty will be used for Equinox Luna.
If 
> that's right, what version of Jetty will be used?
>
> Thanks,
>
> Scott
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev