Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Content-Type: text/plain;
  charset="iso-8859-1"
From: Ryan Bloom <rbb@covalent.net>
Reply-To: rbb@covalent.net
Organization: Covalent Technologies
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>,
	<dev@apr.apache.org>
Subject: Re: multipart/foo rfc2046 parser to suppliment rfc822?
Date: Sat, 1 Sep 2001 00:19:14 -0700
References: <076e01c132a6$072e2870$93c0b0d0@roweclan.net>
In-Reply-To: <076e01c132a6$072e2870$93c0b0d0@roweclan.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <20010901071914.CD71B46993@koj.rkbloom.net>

On Friday 31 August 2001 22:21, William A. Rowe, Jr. wrote:
> Justin, Ryan,
>
>   it seems there are now two interesting rfc822+ Apache apps out there
> (pop and mbox) and I was wondering... do either of you already have the
> multipart parsing that we could move to apr-util (along with rfc822) to
> implement Martin's suggestion of using multipart/alternative (server side)
> over the quick-hack .var map files I implemented?
>
>   Note that rfc2046 and it's successors define a _single_ legitimate
> parsing strategy for multipart documents.  Therefore, this parser is simply
> implemented in terms of rfc822 headers, and the new body semantics.
>
>   I think these _very_ common parsers belong in apr-util (if rfc822 isn't
> already there, I'm working from memory.)

The pop module uses an incredibly simplistic parser, because that is all it
requires.  Sorry.

Ryan

______________________________________________________________
Ryan Bloom				rbb@apache.org
Covalent Technologies			rbb@covalent.net
--------------------------------------------------------------