X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fintroduction.xml;h=b8f136b85115085c4e20581a8568a79c9620a963;hb=f7471d960fb2671c714bdfcd74dae39ce8112652;hp=4ddb58ffd1def73697c49289c58abd2c0dd441f8;hpb=bb96685811b1601d9453b3ecfb67368cb37e7afb;p=yaz-moved-to-github.git diff --git a/doc/introduction.xml b/doc/introduction.xml index 4ddb58f..b8f136b 100644 --- a/doc/introduction.xml +++ b/doc/introduction.xml @@ -1,4 +1,4 @@ - + Introduction @@ -13,18 +13,19 @@ It is, by far, the easiest way to develop clients in C. Server implementers should consider the generic frontend server. - None of those high-level API's support the whole protocol, but - they support most facilities used in existing Z39.50 + None of those high-level APIs support the whole protocol, but + they do include most facilities used in existing Z39.50 applications. - If you're developing non-standard extensions to Z39.50 or you're + If you're using 'exotic' functionality (meaning anything not included in + the high-level APIs), developing non-standard extensions to Z39.50 or you're going to develop an ILL application you'll have to learn the lower - level API's of &yaz;. + level APIs of &yaz;. - The basic low level modules, which is independent of the role, - consists of three primary interfaces: + The basic low level modules, which are independent of the role (client or server), + consist of three primary interfaces: &asn;, which provides a C representation of the Z39.50