[WEBSOCKET_SPEC-224] Consider NOOP default interface methods implementation - Encoder/Decoder init/destroy - Java SE 8 Created: 01/Apr/14  Updated: 01/Apr/14

Status: Open
Project: websocket-spec
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 2.0

Type: Improvement Priority: Major
Reporter: Pavel Bucek Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified





[WEBSOCKET_SPEC-183] Potential for developer error when configuring decoders and message handlers on programmatic endpoints. Created: 15/Apr/13  Updated: 15/Apr/13

Status: Open
Project: websocket-spec
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 2.0

Type: Bug Priority: Minor
Reporter: dannycoward Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

For programmatic endpoints, the decoders are configured when creating the endpointconfig. i.e. before the endpoint is brought into service. But the message handlers are configured dynamically on the session object, i.e. after the endpoint has been brought into service.

Since certain MessageHandlers may need specific Decoders, there is a potential for error since they are configured at different times.

We should explore ways to configure them at the same time in the next version.






Generated at Mon Apr 27 17:42:47 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.