websocket-spec
  1. websocket-spec
  2. WEBSOCKET_SPEC-69

Publish same programmatic endpoint type to many different paths

    Details

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

      Description

      I think the "publishServer" method parameter in ServerContainer class should be modified:
      instead of receiving a "class" (that was needed in revision 49 to create an endpoint instance per peer), wouldn't it be more useful now to receive a ServerEndpointConfiguration instance object?

      i.e:

      Supposing it had the following method's signature:

      void publishServer(ServerEndpointConfiguration config)
      throws DeploymentException;

      Then, it could be possible to register the same endpoint type with many different configurations.

      i.e:

      theServerContainer.publishServer(new MyChatRoomServerEndpointConfiguration("/room1"));

      theServerContainer.publishServer(new MyChatRoomServerEndpointConfiguration("/room2"));

        Issue Links

          Activity

          Hide
          dannycoward added a comment -

          The updated ServerApplicationConfiguration and cleaned up configuration APIs in v013 allow
          the same config class to be instantiated with different properties and used to deploy
          the same endpoint class in various different configured states (including to multiple paths).

          There is a separate RFE files for programmatic deployment, so I am closing this one out.

          Show
          dannycoward added a comment - The updated ServerApplicationConfiguration and cleaned up configuration APIs in v013 allow the same config class to be instantiated with different properties and used to deploy the same endpoint class in various different configured states (including to multiple paths). There is a separate RFE files for programmatic deployment, so I am closing this one out.

            People

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

              Dates

              • Due:
                Created:
                Updated:
                Resolved: