<< Back to previous view

[SIPSERVLET_SPEC-28] Compact header form behavior unclear Created: 17/Jan/13  Updated: 26/Mar/14  Resolved: 07/Feb/14

Status: Resolved
Project: sipservlet-spec
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0-pr

Type: Improvement Priority: Major
Reporter: echeung Assignee: binod
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags:
Participants: binod and echeung

 Description   

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.



 Comments   
Comment by binod [ 10/Dec/13 11:20 AM ]

Now that we have a new method getHeaderNameList(), would it make sense to specify long and compact name behavior only to the new method or should we also specify the behavior of getHeaderNames?

Comment by binod [ 07/Feb/14 11:16 AM ]

As per the EG discussion, we decided that both getHeaderNames and getHeaderNameList will return header names in the long format. The implementations seem to be comfortable with this change and will not introduce backward incompatibility.

Generated at Wed Apr 16 19:05:55 UTC 2014 using JIRA 4.0.2#472.