Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-97
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: dannycoward
Reporter: dannycoward
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
websocket-spec

Consider using jax-rs MultiValueMap to represent Http headers in the handshake request and response

Created: 08/Jan/13 12:00 AM   Updated: 16/Feb/13 01:11 AM  Due: 08/Feb/13   Resolved: 16/Feb/13 01:11 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags: v013
Participants: dannycoward and jitu


 Description  « Hide

as synopsis.

Of not, will need to clarify the representation of http headers like this:-

headernameA: value1
headernameA: value2

should it be represented as

headernameA: value1, value2

?



jitu added a comment - 08/Jan/13 12:29 AM

MultivaluedMap is just a sub type of Map<String, List<String>> and it adds some utility methods like getFirst(K key).

Other than that, MultivaluedMap doesn't give any other serialization semantics as mentioned in the report. As far as HTTP is considered, both forms are equivalent. API doesn't have to prefer one form over the other.


dannycoward added a comment - 16/Feb/13 01:11 AM

I raised the possibility of using the JAX-RS multvaluedmap for headers on the expert group, it seems the sentiment is that for the couple of utility methods, its not worth the websocket spec building a dependency on that API. So we will keep the headers as they are.