Thilina Gunarathne wrote: >> Does Axis, or Axiom, handle the Base64 encoding/decoding of the binary >> data to/from a DataHandler? > Yes... Only if needed... > >> If so, is there a way to disable such handling? > Nope... But if you use the API properly you can avoid any unncessary > encoding/decodings. > >> Characteristics for my service have a client submitting large files and >> then some number of clients retrieving them. The service itself treats >> these files as opaque blobs. It could receive, and return, them to Axis >> in a Base64 encoded form saving a lot of time when clients retrieved a >> document be avoiding a re-encode. > Above is not clear to me. Is your service written in Axis2. Do you > want to send/receive binary in base64 form.. If so it won't tolerate > large files..
I'm not using anything yet. My hope was to use Axis2 so right now I'm just trying to make sure it supports what I'll need. I know that the need to send large files, encoded as base64 element content, is not something that most SOAP stacks handle. This is why I started by asking about true end-to-end streaming support when using MTOM. If, as we discussed in the first part of this thread, Axis2/Axiom supports true end-to-end streaming, and Axiom can correctly stream content from/into a DataHandler, what causes problems for arbitrarily large files? Maybe I misunderstood something in the first part of the thread or didn't properly state what I was trying to accomplish. -- Chad La Joie 2052-C Harris Bldg OIS-Middleware 202.687.0124 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
