I am trying to understand this interop issue in relation to my
applications requirements.

My clients are sending a .war file as an attachment to my service. My
client is adding it as an attachment using a ByteArrayDataSource. The
server gets the DataHandler InputStream and streams the content to file
or DB. The client is using DIME. 

In order to interoperate with all SOAP(DIME) clients does the client
have to Base64 encode the .war byte[] before adding the attachment or
will this byte[] get encoded by DIME and be properly decoded by any DIME
client? 

Looking at the attachment I am not sure what encoding it is or if it is
just java serialization and if so only a java client could read the
attachment?

I am obviously confused and would appreciate any clarification.

Thanks for you time,

Greg

> -----Original Message-----
> From: Dave Simmons [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 12, 2003 1:12 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Custom mapping's and DataHandlers?
> 
> 
> Yes, Base64 encoding increases the size of the binary data by 33% over
the
> pure binary encoding that axis will use for multipart or DataHandler
> encoding.
> 
> It's a tradeoff -- use Base64 and interoperate with all SOAP clients
(but
> increase server coding effort and message size), use DIME and interop
with
> some, use DataHandler objects and be compatible only with java axis
> clients.
> 
> Which approach is best for you depends on what SOAP client toolkits
your
> server needs to be compatible with.  If you have enough control over
the
> client side to demand that all clients be written in java and use axis
> (both now and in the future) then DataHandlers are worth using for the
> pure
> binary encoding vs. Base64.
> 
> ---Dave
> 
> 
> At 05:17 PM 11/11/2003 -0800, you wrote:
> >If I understood you correctly, you are suggesting that binary data
should
> >be encoded with Base64 inside of the SOAP message itself.  Many of
the
> >articles I have read have said that Base64 encoding within the SOAP
> >message is inefficient. For example here  are two  articles -
> >
> >http://www.pocketsoap.com/pocketsoap/docs/master/attachments.htm
> >                 http://www.xml.com/pub/a/2003/02/26/binaryxml.html
> >
> >What are your comments?


Reply via email to