[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] [rt-pmc] Draft graduation/release review docuware for Virgo and Gemini Web
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Fri, 17 Sep 2010 00:31:16 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: email@example.com
- Thread-index: ActWOlCcbVhsCIj3TjaQJctrYuMWbA==
- Thread-topic: [rt-pmc] Draft graduation/release review docuware for Virgo and Gemini Web
We originally anticipated supporting Jetty in Virgo by supporting Jetty in Gemini Web. However, it appears that Jetty has been tracking RFC 66 and has its own implementation of the OSGi Web Applications specification. So, from that perspective, it is more natural to consider Jetty a functional superset of Gemini Web. So we are now proposing to support Jetty directly in Virgo as an alternative to Gemini Web. Does this seem reasonable? Maybe Jetty folks would care to comment.
On 16 Sep 2010, at 18:48, Jeff McAffer wrote:
> Overall they look good. Well done. I did note in the Gemini version there were no plans listed for enabling Jetty integration. That feels like the same discussion we had in the Virgo context. I believe it should be an RT imperative that where there exists a reasonable implementation at Eclipse, it should be used or usable. We want people to be able to come to RT and get pieces that fit together and not end up with N server/database/UI/... technologies.
> On 2010-09-16, at 6:10 AM, Glyn Normington wrote:
>> I would be grateful for any feedback on the attached draft docuware.
>> Please note that if Gemini graduates out of incubation before we need to submit the Gemini Web docuware, we'll be able to drop the graduation aspects of that docuware.
>> rt-pmc mailing list
> rt-pmc mailing list