How to build the DataDDX response in/with Hyrax: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Line 1: | Line 1: | ||
== Suggested Division of Labor == | == Suggested Division of Labor == | ||
[[Image:DAP4 DataDDX Design 2.png|400px|frame|Building the DataDDX with the OLFS making the initial and final headers. The BES/libdap/handler will have to make the 'part' headers except for the closing segment. This provides an easy way for the OLFS to combine several DataDDX responses in a single MP MIME document (easy in the sense that the OLFS does not have to pull apart the response from the BES).]] | [[Image:DAP4 DataDDX Design 2.png|400px|right|frame|Building the DataDDX with the OLFS making the initial and final headers. The BES/libdap/handler will have to make the 'part' headers except for the closing segment. This provides an easy way for the OLFS to combine several DataDDX responses in a single MP MIME document (easy in the sense that the OLFS does not have to pull apart the response from the BES).]] | ||
[[Image:DAP4 DataDDX Design 1.png|right|thumb|This design would be good form the standpoint of support for protocols that don't want data responses in multipart MIME documents, but it's far from optimal since the DDS has to be built twice for each request]] | [[Image:DAP4 DataDDX Design 1.png|right|thumb|This design would be good form the standpoint of support for protocols that don't want data responses in multipart MIME documents, but it's far from optimal since the DDS has to be built twice for each request]] |