https://docs.opendap.org/index.php?action=history&feed=atom&title=Use_of_MIME 2026-06-18T05:04:42Z Revision history for this page on the wiki MediaWiki 1.38.4 https://docs.opendap.org/index.php?title=Use_of_MIME&diff=2228&oldid=prev 2008-06-24T21:11:17Z

<p>New page: I think that we should specify that MIME documents are used to hold the objects/responses. James Gallagher - 26 Sep 2003 Ok, do you envision doing away with the separate blob response?...</p> <p><b>New page</b></p><div><br /> I think that we should specify that MIME documents are used to hold the objects/responses. <br /> <br /> James Gallagher - 26 Sep 2003<br /> <br /> Ok, do you envision doing away with the separate blob response? <br /> <br /> Nathan Potter - 26 Sep 2003<br /> <br /> Nope. We need the BLOB to be separate because quasi-transports like SOAP require the entire response be complete before transmission starts. We want to support streaming, so we need to make the data available w/o involving SOAP, for example. Since MIME does not _have_ to include =Content-Length= we can stream a MIME document.<br /> <br /> Along these same lines, using the MIME/multipart for the BLOB (see BlobFormatting) we can support stuff like HTTP keep-alive (because it&#039;s possible to tell when the stream ends since multipart specifies a trailing =boundary= marker). This is a big win for efficiency - we want to be able to support the more advanced features of HTTP even though we don&#039;t want to tie the DAP4 to HTTP.<br /> <br /> James Gallagher - 26 Sep 2003<br /> <br /> Well, this is sort of related (perhaps change this topic header to &quot;on-the-wire specification&quot;?)<br /> <br /> I think we need a rigorous specification of what the &quot;on-the-wire&quot; protocol is. As part of that we need to know what is a legal request and response. Right now we have the situation that the HDF server can put out a DDS that breaks the Java parser. Which side has the bug?<br /> <br /> John Caron - 22 Oct 2003</div>

Jimg