james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <server-...@james.apache.org>
Subject [jira] Created: (MIME4J-22) [JW#2]
Date Mon, 06 Aug 2007 20:19:59 GMT
[JW#2] 
-------

                 Key: MIME4J-22
                 URL: https://issues.apache.org/jira/browse/MIME4J-22
             Project: Mime4j
          Issue Type: Wish
            Reporter: Robert Burrell Donkin


http://mail-archives.apache.org/mod_mbox/james-server-dev/200708.mbox/%3ce75283b10708051908w38b3b7b5l31ef423d33efe014@mail.gmail.com%3e
number 2

2.) Let BodyDescriptor provide full blown access to the headers

      Currently, BodyDescriptor offers access to the content-type and
      content-transfer-encoding headers only.

     As a consequence, the mime4j user is forced to listen for T_FIELD events
     and build its own header map. This is duplicated work, in
particular, because
     all mime4j users will likely do the same.

     I'd propose to:

       - Replace BodyDescriptor with an interface. (Assumes that this
is possible,
         I am guessing by the version number 0.4, but I maybe wrong.)
       - Make the BodyDescriptor implementation pluggable by adding a method

           protected void newBodyDescriptor()

         to the Mime4JTokenStream.
       - Provide a default implementation that maintains a map of headers and
         values.
       - Open up the method

             private void getHeaderParams(String)

         by making it static and moving it to a utility class or by
providing an accessor
         that takes a header name as an argument and invokes the
method by providing
         the value as input.
       - Rename getParameters() to getContentTypeParameters(),
because the method
         name is definitely confusing. I clearly had the impression
that this method would
         provide the header values.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message