[WEBSOCKET_SPEC-159] Encoder/Decoder#setEndpointConfig Created: 04/Mar/13  Updated: 06/Mar/13  Resolved: 06/Mar/13

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

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

Issue Links:
Dependency
blocks TYRUS-122 Implement Encoder/Decoder#init(Endpoi... Resolved
Tags: proposedfinaldraft

 Description   
    /**
     * This method is called with the endpoint configuration object of the
     * endpoint this decoder is intended for when
     * it is about to be brought into service, and with {@code null} when
     * the implementation has finished using it.
     *
     * @param config the endpoint configuration object if being brought into use
     * or {@code null} if being taken out of use.
     */
    void setEndpointConfig(EndpointConfig config);

please rename to something else(/or adjust documentation). This is not "setter", this is lifecycle controller.

Additionally, consider changing Encoder/Decoder to abstract class which has setEndpointConfig implemented, because it is not needed for majority of implementations (educated guess).



 Comments   
Comment by dannycoward [ 06/Mar/13 ]

The APi has been renamed to follow the init()/destroy() pattern of the servlet api.

Encoder and Decoder now have Adapter implementations as a convenience for developers who don't need to do anything with the lifecycle methods.

Generated at Sat Aug 01 12:17:10 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.