[WEBSOCKET_SPEC-49] Consider merging Endpoint with Endpoint configuration Created: 25/Oct/12  Updated: 30/Nov/12  Due: 16/Nov/12  Resolved: 30/Nov/12

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

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


 Description   

Suggested by Martin: It seems that a single endpoint implementation can not be used both on the client and the server side (i.e. I can't think of a use-case where the implementation of both would be the same), also it does not make sense to share the same configuration for multiple endpoints (since that would mean they are all published at the same URI). So why not merging Endpoint and EndpointConfiguration? With a client and server API, we could have ServerEndpoint and ClientEndpoint classes (and delete all *EndpointConfiguration classes - move their methods directly to the Endpoint classes). I think it would simplify it for the users.



 Comments   
Comment by dannycoward [ 30/Nov/12 ]

We will not fix this. At one point in the design there was a rational argument for it (simplicity), but now we have one config per logical endpoint and one endpoint instance per connection, it no longer is possible

Generated at Tue Mar 31 11:31:12 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.