[WEBSOCKET_SPEC-69]  Publish same programmatic endpoint type to many different paths Created: 09/Dec/12  Updated: 16/Feb/13  Due: 08/Feb/13  Resolved: 16/Feb/13

Status: Resolved
Project: websocket-spec
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: jmarine Assignee: dannycoward
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is related to WEBSOCKET_SPEC-114 Programmatic deployment of server end... Resolved
is related to WEBSOCKET_SPEC-116 WebSocketContainer.connectToServer ea... Resolved
Tags: v013


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?


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.


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

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

Comment by dannycoward [ 16/Feb/13 ]

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.

Generated at Tue Jul 07 02:58:31 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.