[Rets-dev] RETS manifest

[dbt]

On Wed, Jul 26, 2006 at 01:07:09AM -0400, Jeff Brush wrote:
> >From the MTOM spec: "Optimization is available only for element content
> that is in a canonical lexical representation of the xs:base64Binary data
> type."
> 
> So a base64Binary data type signals the optimizer to put raw,
> unencoded data bytes into a multipart attachment. This is what MTOM does - 
> raw un-base64 encoded data in an attachment and an XOP tag taking the 
> base64Binary data's place. Period. (Some toolkits seem to support hexBinary 
> as well.)

I can certainly see why this is superior to providing a url that the 
end-user application can simply download.

*boggle*

I'm willing to stipulate that SOAP is ok for structured data transmission
for the sake of this discussion.  Why are we trying to stuff massive
amounts of binary data over the wire in XML?  It's always going to be
stupider and harder and more fragile than streaming a simple HTTP request.