DAP4: DAP4 Using Multi-part Mime
From OPeNDAP Documentation
Revision as of 22:34, 19 March 2013 by DennisHeimbigner (talk | contribs) (Created page with "DevelopmentDAP4 << Back to OPULS Development ==Background== After thinking about it as a result of a comment in...")
Background
After thinking about it as a result of a comment in the OPULS/NOAA telecon, I think we should reconsider using multi-part mime in a limited fashion in our serialization.
Problem Addressed
The primary reason for this proposal is so that our serialized form will "obey the forms" of HTTP more closely. It is not essential, but I think it would make our serialization play better with existing HTTP technology.
My original objection to using multi-part mime was that it would, I thought, slow up decoding of the serialization because of the need to search for the UID separator lines. The following proposal tries to simplify the use of multi-part mime so that it has minimal impact on performance.
