6 The MXG Protocol The MXG protocol consists of a Request made by the Metasearch Service (MS) to the Content Provider's (CP) resource and a Response from the CP to the MS. [...] (See section 6.2.1.2 for a description of providing the resultSetId in a Response record.) An example of a URL with a result set reference that asks for the second record of the result set is: abc123&startRecord=2&maximumRecords=1 The alternative to using a resultSetId is to reissue the original query with a new startRecord par. [...] 6.2.1.2 Result Set Elements The next group of elements in the MXG XML Response describes the result set and takes the form: 717zar 30 If the CP server generates result sets that can be referenced after the query is complete, then this is where it will specify the identifier for the result set and indicate how long the result set wil. [...] The Explain operation consists of: 1) a request from the client that contains the operation=explain parameter; and 2) a response from the server that includes the Explain record describing the server's capabilities. [...] client/server A computing architecture that separates application functionality between two computers on a network; a client makes a request to a server, which performs the necessary services to process the request and returns the requested information to the client; the client may then do further post-processing of the data received from the server.
Authors
- Pages
- 24
- Published in
- United States of America
- Title in English
- NISO Metasearch Initiative - Metasearch XML Gateway Implementers Guide [from PDF fonts]