[WEBSOCKET_SPEC-50] Do we need ContainerProvider.getServerContainer() ? Created: 25/Oct/12 Updated: 17/Nov/12 Due: 09/Nov/12 Resolved: 17/Nov/12
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
WebSockets supported on Web Containers can do their own bootstrapping and selection of implementation. So does the developer API really need to define this entry point ?
On the other hand, since people may want to define standalone web socket servers, outside the context of the web container, won't they need some standard way to get the ServerContainer and deploy their endpoints ? Or is it ok for that part of their deployment of web sockets on standalone websocket servers to be proprietary ?
|Comment by dannycoward [ 17/Nov/12 ]|
We floated the idea of using the ServiceLoader, but this way seems cleaner and consistent with other specs.