X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fzoom.xml;h=e61a14e47a166dda0b8e410c44778ec37408a00a;hb=ae166973a7ad342554ec7cd39135561523a3083f;hp=e767d9b608dd358be5cf8c98f8f611c083f6baa9;hpb=da58ec3f2b9c0e5d15e4a022e7072f573784f9eb;p=yazpp-moved-to-github.git diff --git a/doc/zoom.xml b/doc/zoom.xml index e767d9b..e61a14e 100644 --- a/doc/zoom.xml +++ b/doc/zoom.xml @@ -1,5 +1,5 @@ - + ZOOM-C++ @@ -17,14 +17,14 @@ programming languages. - The Yaz++ library includes an implementation of the C++ binding for ZOOM, enabling quick, easy development of client applications. For example, here is a tiny Z39.50 client that fetches and displays - the MARC record for Farlow & Brett Surman's + the MARC record for Farlow & Brett Surman's The Complete Dinosaur from the Library of Congress's Z39.50 server: @@ -52,11 +52,11 @@ - Yaz++'s implementation of the C++ binding is a thin layer over Yaz's + YAZ++'s implementation of the C++ binding is a thin layer over YAZ's implementation of the C binding. For information on the supported options and other such details, see the ZOOM-C documentation, which can be found on-line at - + All of the classes defined by ZOOM-C++ are in the @@ -157,7 +157,7 @@ - The Connections section of the ZOOM-C documentation @@ -185,9 +185,9 @@ }; - This class enables a query to be created by compiling Yaz's + This class enables a query to be created by compiling YAZ's cryptic but powerful - Prefix Query Notation (PQN). @@ -204,10 +204,10 @@ This class enables a query to be created using the simpler but less expressive - Common Command Language (CCL). The qualifiers recognised by the CCL parser are specified in an - external configuration file in the format described by the Yaz + external configuration file in the format described by the YAZ documentation. @@ -257,7 +257,7 @@ - The Queries section of the ZOOM-C documentation @@ -339,7 +339,7 @@ - The Result Sets section of the ZOOM-C documentation @@ -423,7 +423,7 @@ Memory Management - The record obejcts returned from + The record objects returned from resultSet::getRecord() are ``owned'' by the result set object: that means that the application is not responsible for deleteing them - each @@ -469,7 +469,7 @@ - The Records section of the ZOOM-C documentation @@ -667,7 +667,7 @@ exception class and its subclasses. The closest thing is the ZOOM_connection_error function described in - The Connections section of the documentation.