Re: [equinox-dev] Any consumers of the org.eclipse.equinox.http bundle?
WTP does not appear to ... though they do use org.eclipse.equinox.http.jetty. But ... a note to cross-project list might better reach your intended audience (I know ... I too can not believe everyone does not follow equinox-dev ... but, just in case :) From: Thomas Watson/Austin/IBM@IBMUS To: equinox-dev@eclipse.org Date: 10/27/2011 02:29 PM Subject:[equinox-dev] Any consumers of the org.eclipse.equinox.http bundle? Sent by:equinox-dev-boun...@eclipse.org In Equinox we have a two implementations of the HttpService. 1) org.eclipse.equinox.http - that has a home grown web container and therefore has to implement the complete servlet specification itself. 2) org.eclipse.equinox.http.jetty - that is uses a jetty implementation for the web container implementation. The implementation that uses jetty is by far the most used HttpService implementation we have. For example, it is the one shipped with the eclipse SDK to serve up the help and is used in the server-side equinox project. The old org.eclipse.equinox.http is outdated and gets very little attention by the committers. As we consider moving to support servlet 3.0 and Jetty 8 we also need to consider what, if anything, should be done for the old stand-alone HttpService bundle org.eclipse.equinox.http. For Juno I propose that the Equinox project stops building the old stand-alone HttpService implementation bundle org.eclipse.equinox.http. I would much prefer we focus on the implementation of the HttpService that uses Jetty and keep the implementation of the servlet container in the hands of the experts that know how to implement it (i.e. the jetty team). Please voice any concerns to this mailing list or to the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=362217 Thanks. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] Any consumers of the org.eclipse.equinox.http bundle?
Some p2 tests use that bundle. They could probably changed to use the other bundle. On 2011-10-27, at 2:18 PM, Thomas Watson wrote: > In Equinox we have a two implementations of the HttpService. > > 1) org.eclipse.equinox.http - that has a home grown web container and > therefore has to implement the complete servlet specification itself. > 2) org.eclipse.equinox.http.jetty - that is uses a jetty implementation for > the web container implementation. > > The implementation that uses jetty is by far the most used HttpService > implementation we have. For example, it is the one shipped with the eclipse > SDK to serve up the help and is used in the server-side equinox project. The > old org.eclipse.equinox.http is outdated and gets very little attention by > the committers. As we consider moving to support servlet 3.0 and Jetty 8 we > also need to consider what, if anything, should be done for the old > stand-alone HttpService bundle org.eclipse.equinox.http. > > For Juno I propose that the Equinox project stops building the old > stand-alone HttpService implementation bundle org.eclipse.equinox.http. I > would much prefer we focus on the implementation of the HttpService that uses > Jetty and keep the implementation of the servlet container in the hands of > the experts that know how to implement it (i.e. the jetty team). > > Please voice any concerns to this mailing list or to the bug > https://bugs.eclipse.org/bugs/show_bug.cgi?id=362217 > > Thanks. > > Tom > > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Any consumers of the org.eclipse.equinox.http bundle?
In Equinox we have a two implementations of the HttpService. 1) org.eclipse.equinox.http - that has a home grown web container and therefore has to implement the complete servlet specification itself. 2) org.eclipse.equinox.http.jetty - that is uses a jetty implementation for the web container implementation. The implementation that uses jetty is by far the most used HttpService implementation we have. For example, it is the one shipped with the eclipse SDK to serve up the help and is used in the server-side equinox project. The old org.eclipse.equinox.http is outdated and gets very little attention by the committers. As we consider moving to support servlet 3.0 and Jetty 8 we also need to consider what, if anything, should be done for the old stand-alone HttpService bundle org.eclipse.equinox.http. For Juno I propose that the Equinox project stops building the old stand-alone HttpService implementation bundle org.eclipse.equinox.http. I would much prefer we focus on the implementation of the HttpService that uses Jetty and keep the implementation of the servlet container in the hands of the experts that know how to implement it (i.e. the jetty team). Please voice any concerns to this mailing list or to the bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=362217 Thanks. Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
