[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-dev] Jetty 9 + Websocket Modules
|
Not also that the whole process of exposing proprietary APIs in a web
app is fraught with making very version dependent dependencies between
a webapp and the container.
If you want to get some level of webapp portability - even between
versions of jetty, then you have to have an extra layer. For examples
the jetty-continuation module is included in WEB-INF/lib and smooths
over the differences in the implementations between jetty-6,7,8 & 9 so
the webapp will work on all of those even though jetty 6 and 9 both
lack native continuation support!
We should look to do the same with JSR-356. Instead of trying to make
our websocket API immutable and portable, we should just make our
containers provide JSR-356 implementations that use the native
websocket support. Ideally we could even do this with jetty-7/8
websockets so the one webapp would work on jetty 7, 8 or 9 (or tomcat
etc). This is much less work than making our our API the
portability layer.
cheers