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] Updated: (MIME4J-21) [JW #1] Parsing a message without headers
Date Mon, 06 Aug 2007 20:19:59 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Burrell Donkin updated MIME4J-21:
----------------------------------------

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

    Currently, Mime4j can only parse messages with headers. That's
not suitable
      for parsing an HTTP message, because the typical situation is
in a servlet,
      that doesn't see the headers.

      I'd propose a new method

           public parse(InputStream, BodyDescriptor)

     This method would be specified as emitting a sequence

         T_START_MULTIPART ... T_END_MULTIPART

     as opposed to

         T_START_MESSAGE T_START_HEADER ... T_END_HEADER
         T_START_MULTIPART ... T_END_MULTIPART T_END_MESSAGE

     The required patch is relatively minor and should not complicate
the parser.


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

        Summary: [JW #1] Parsing a message without headers  (was: [JochenParsing a message
without headers)

> [JW #1] Parsing a message without headers
> -----------------------------------------
>
>                 Key: MIME4J-21
>                 URL: https://issues.apache.org/jira/browse/MIME4J-21
>             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
#1
>     Currently, Mime4j can only parse messages with headers. That's
> not suitable
>       for parsing an HTTP message, because the typical situation is
> in a servlet,
>       that doesn't see the headers.
>       I'd propose a new method
>            public parse(InputStream, BodyDescriptor)
>      This method would be specified as emitting a sequence
>          T_START_MULTIPART ... T_END_MULTIPART
>      as opposed to
>          T_START_MESSAGE T_START_HEADER ... T_END_HEADER
>          T_START_MULTIPART ... T_END_MULTIPART T_END_MESSAGE
>      The required patch is relatively minor and should not complicate
> the parser.

-- 
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