Sorry, I have one more question related to this topic.
Does Axis, or Axiom, handle the Base64 encoding/decoding of the binary
data to/from a DataHandler? If so, is there a way to disable such handling?
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.
Chad La Joie wrote:
I'm working on a project that may (read: almost certainly will) require
very large binary blobs (many GBs) to be transported. The specification
I'm working with requires at least SOAP over HTTP support and allows for
the use of MTOM.
My question is, does Axis 2 (client and service side) support true
end-to-end streaming. By this I mean can a service stream data from
disk, over HTTP to the client and provide a stream on the client side
which can be dumped direct to disk?
I had read the MTOM guide [1] and while I see data handlers and sources
being used it doesn't say whether Axis 2 is architected in such a way
that the data is never buffered in memory.
Thanks for the help.
[1] http://ws.apache.org/axis2/1_0/mtom-guide.html
--
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]
