MIME does use separators (called boundaries in MIME). The code generating the MIME boundary is required to guarantee that the boundary doesn't appear in the payload.
Cheers
Simon
-----Original Message-----
From: Dennis Sosnoski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 1:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Interoperative attachments
I thought MIME used separators, which would mean it requires some sort
of encoding/escaping to avoid the separator appearing in data. How
*does* MIME handle delimiting parts?
- Dennis
Simon Fell wrote:
> It doesn't when transported over an 8 bit clean transport (such as
> http), although Apache SOAP would encode it anyway, don't know if axis
> does. But that is an implementation limitation, not an issue with MIME
> itself.
>
> Cheers
> Simon
> www.pocketsoap.com
>
> -----Original Message-----
> From: Norris Merritt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 1:08 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Interoperative attachments
>
>
> If you have an binary type of attachment such as image/jpeg, then it
> has to
> be Base-64 encoded if MIME is used
>
> -----Original Message-----
> From: Dan Allen [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 28, 2003 12:40 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Interoperative attachments
>
>
>
>
> > -----Original Message-----
> > From: Norris Merritt [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, January 28, 2003 2:09 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Interoperative attachments
> >
> >
> > I've had success with the Axis 1.1 beta DIME support demonstrated in
> the
> > echoAttachments sample (which also has a mode in which it uses
> MIME). Axis
> > 1.1 beta DIME support interoperates both with gSOAP and .NET. For my
> money
> > DIME is the way to go, especially with attachments that would otherwise
> need
> > to be Base-64 encoded. Its much more efficient than MIME.
>
> Why would a MIME attachement need to be Base-64 encoded?
>
> Dan
>
