Issue Details (XML | Word | Printable)

Key: SIPSERVLET_SPEC-28
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: binod
Reporter: echeung
Votes: 0
Watchers: 0
Operations

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

Compact header form behavior unclear

Created: 17/Jan/13 02:51 PM   Updated: 26/Mar/14 04:58 AM   Resolved: 07/Feb/14 11:16 AM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0-pr

Time Tracking:
Not Specified

Tags:
Participants: binod and echeung


 Description  « Hide

The Javadoc of SipServletMessage is unclear:

  • The behavior of getHeaderNames() is unclear. If the message contains both long and compact name of the same header, e.g. Supported and k, should both be returned, or one, and which one?
    (Suggest only one to be consistent to getHeader() and setHeader())

Currently, the application has no knowledge of the header form of an incoming message. The application can influence the header form on an outgoing message. Also note that if there are mixed usage of long and compact forms, there is no way to preserve the forms when copying from one message to another. This may cause problem for some corner interop situations.