websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-50

Do we need ContainerProvider.getServerContainer() ?

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      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 ?

        Activity

        dannycoward created issue -
        dannycoward made changes -
        Field Original Value New Value
        Due Date 2012-11-09 00:00:00.0
        Hide
        dannycoward added a comment -

        We floated the idea of using the ServiceLoader, but this way seems cleaner and consistent with other specs.

        Show
        dannycoward added a comment - We floated the idea of using the ServiceLoader, but this way seems cleaner and consistent with other specs.
        dannycoward made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee dannycoward [ dannycoward ]
        Tags v008
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            dannycoward
            Reporter:
            dannycoward
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved: