[WEBSOCKET_SPEC-71] Allow extension parameters in the API Created: 12/Dec/12  Updated: 14/Dec/12  Resolved: 14/Dec/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

Tags: v010


ServerEndpointConfiguration.getNegotiatedExtensions() takes a List of Strings. Consider allowing Extension parameters passed in with the headers to be passed in to this API as well as the names. (see the RFC)

Comment by dannycoward [ 14/Dec/12 ]

Have added API to support this in v010: called Extension, with name and map of parameters. Where previously the API used List<String> to represent the ordered list of extensions, now it uses List<Extension>.

Generated at Mon Feb 27 13:41:29 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.