Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-pr
    • Labels:
      None

      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.

        Activity

        Hide
        binod added a comment -

        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.

        Show
        binod added a comment - 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.
        Hide
        binod added a comment -

        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?

        Show
        binod added a comment - 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?

          People

          • Assignee:
            binod
            Reporter:
            echeung
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: