Skip to main content

[JIRA] Created: (SIPSERVLET_SPEC-28) Compact header form behavior unclear

  • From: "echeung (JIRA)" < >
  • To:
  • Subject: [JIRA] Created: (SIPSERVLET_SPEC-28) Compact header form behavior unclear
  • Date: Thu, 17 Jan 2013 14:51:53 +0000 (GMT+00:00)
  • Auto-submitted: auto-generated

Compact header form behavior unclear
------------------------------------

                 Key: SIPSERVLET_SPEC-28
                 URL: http://java.net/jira/browse/SIPSERVLET_SPEC-28
             Project: sipservlet-spec
          Issue Type: Improvement
            Reporter: echeung


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://java.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[JIRA] Created: (SIPSERVLET_SPEC-28) Compact header form behavior unclear

echeung (JIRA) 01/17/2013
 
 
Close
loading
Please Confirm
Close