[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-dev] Jetty 9 + Websocket Modules
|
I see the question more about what do we expose in the API for developers to use?
Future seems a reasonable enough level to expose at the API level.
Internally, our impl would still use the Callback class, as that's how we have the new I/O layers created.
I see no real need to expose that level to the developers that want to use websocket.
Only async websocket write uses the Callback classes at the moment.
Ideally, I'd like to fix the namespaces to be more isolated in terms of what they 'let through' in the system classes.
I agree that we shouldn't depend on people putting provided classes/jars in the WEB-INF/lib.
The exercise on how to isolate classes and limit the exposure through the classloader was a thought experiment on what would be used by developers in a dependency sense (mentioning what would go in WEB-INF/lib was merely a way to frame the discussion on what to expose)