I think a MIME Multipart project is a great idea (whether independent or
part of codec), and would be willing to contribute some time to it.
I have written (and continue to maintain) a b2b framework for my
employer. We use ebxml over IBM MQSeries to transfer messages around,
and ebxml uses MIME multipart ("soap with attachments") encoding to
bundle together message bodies with their relevant headers.
See: http://www.w3.org/TR/SOAP-attachments
and: http://webservices.xml.com/pub/a/ws/2003/03/18/ebxml.html
As stated elsewhere, Sun provides some multipart-mime stuff as part of
JavaMail, but this is really heavy and clumsy to work with (far too
mail-focused). All that JAF stuff, for example, just gets in the way.
Sun defines the "saaj" (Soap with Attachments API for Java), and
provides an implementation but this implementation depends on JAF and
JavaMail; again *way* too heavy for my purposes.
See: http://java.sun.com/xml/saaj/index.jsp
and: http://java.sun.com/webservices/docs/1.3/saaj/ReleaseNotes.html
I've got some horrible kludges coded up at the moment to do mime stuff,
but would be happy to help out with a proper generic mime multipart
library.
Cheers,
Simon
On Sat, 2004-01-10 at 17:45, Martin Cooper wrote:
> If we're going to put this MIME thingy together, it would seem that the
> issues being faced by James would provide a nice set of design criteria to
> add to the puzzle. A robust MIME library that would satisfy the needs of
> James, HttpClient, FileUpload, and possibly others, would be awesome.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
