> Even with MIME or DIME, the binary data is sent in base64binary or
> hexbinary.
Not true.. They can be sent as Binary when used with transport
protocols which supports binary (eg: http)..
>The difference is it is not send as a part of the soap
> message. The difference is akin to attaching a jpeg image to an email
> rather than pasting the image in the body of the email.
Attachments get base64 encoded in emails as smtp is a text protocol.

There are two advantages in sending Binary as attachments. First is
your message does not get bloated due to encoding. Second is you are
not encoding binary, which will save you some CPU cycles at the
sending as well as in the receiving end.

thanks,
Thilina
>
>
> - Vishwajit.
>
> >-----Original Message-----
> >From: Walker, Jeff [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, July 31, 2007 6:07 AM
> >To: [email protected]
> >Subject: RE: Sending pictures or files through Web Services
> >
> >With Base64, there is an approx. 33% increase in the size of the
> >payload. That's a huge cost, considering all you're trying to do is
> >transfer a file from point A to B. If you always know the size of your
> >attachments, then you know up front the cost it brings to the table,
> and
> >then I guess Base64 would look more acceptable. To most people creating
> >web services, they don't know up front the cost of different parts of
> >their applications, on average, especially the size of attachments that
> >a person could add to the web service invocation.
> >Base64 is definitely the simplest. There are numerous examples out
> >there.
> >SWA and DIME are superseded by MTOM.
> >-jeff
> >
> >
> >-----Original Message-----
> >From: Erwin Reinhoud [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, July 31, 2007 3:03 AM
> >To: [email protected]
> >Subject: RE: Sending pictures or files through Web Services
> >
> >Hello,
> >
> >This is more another question than an answer, but why not use just
> >base64Binary in the payload? I know it adds to size and processing, but
> >as long as size stays in limits isn't this a good interoperable
> >alternative?
> >
> >Any comments?
> >
> >Thanks in advance.
> >
> >Greetings,
> >
> >Erwin
> >
> >-----Oorspronkelijk bericht-----
> >Van: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED]
> >Verzonden: maandag 30 juli 2007 22:59
> >Aan: [email protected]
> >Onderwerp: RE: Sending pictures or files through Web Services
> >
> >
> >For attachments with Axis1, you will probably end up using MIME, except
> >if the client is .NET based - then you will need to use DIME format
> >instead of MIME as Microsoft does not support MIME based attachments
> for
> >webservices.
> >
> >
> >- Vishwajit.
> >
> >
> >>-----Original Message-----
> >>From: Anthony Bull [mailto:[EMAIL PROTECTED]
> >>Sent: Monday, July 30, 2007 1:49 PM
> >>To: [email protected]
> >>Subject: Re: Sending pictures or files through Web Services
> >>
> >>Hi David,
> >>
> >>I'm currently doing a project at work that requires the transmission
> of
> >>a file as part of a SOAP message. I'm only starting to implement it
> >>today, but I'm using the SOAP with attachments features in Axis2 (I
> >>don't know about Axis 1 support for it).  The following article is
> what
> >>I started from, and it is working well:
> >>
> >>http://wso2.org/library/1148
> >>
> >>cheers,
> >>Ants.
> >>
> >>at4david wrote:
> >>> Hi, I am starting to implement web services using Apache Axis and
> >Java.
> >>> I need to send files how pictures or others through Web Services and
> >I
> >>would
> >>> like to know how do it.
> >>>
> >>> I want to do that a client request for a specific picture to web
> >service
> >>and
> >>> Web Service will send requested picture to the client in its
> >response, is
> >>it
> >>> possible to do it with Web Services???
> >>>
> >>> The client requests a picture and Web Service replies sending a
> >picture
> >>to
> >>> the client, this is the idea.
> >>>
> >>>
> >>>
> >>> Thanks in advance
> >>>
> >>
> >>
> >>--
> >>Anthony
> >>-------------------------------------
> >>Anthony Bull
> >>Senior Developer
> >>Black Coffee Software Ltd
> >>PO Box 10-192 The Terrace
> >>Wellington, New Zealand
> >>
> >>[EMAIL PROTECTED]
> >>Ph  +64 4 472 8818
> >>Fax +64 4 472 8811
> >>Mobile 021 303 692
> >>-------------------------------------
> >>www.bcsoft.co.nz
> >>---------------------------------------------------------------
> >>This email may contain confidential or privileged information,
> >>and is intended for use only by the addressee, or addressees.
> >>If you are not the intended recipient please advise the sender
> >>immediately and do not copy, use or disclose the contents to
> >>any other person or organisation.
> >>Black Coffee Software Ltd accepts no responsibility for viruses
> >>received with this email, or to any changes made to the original
> >>content. Any views or opinions expressed in this email may be
> >>personal to the sender and are not necessarily those of Black
> >>Coffee Software Ltd.
> >>---------------------------------------------------------------
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thilina Gunarathne  -  http://www.wso2.com - http://thilinag.blogspot.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to