X-Git-Url: http://lists.indexdata.com/cgi-bin?a=blobdiff_plain;ds=sidebyside;f=doc%2Fadministration.xml;h=cd0572e9f661132d6a3ec5b36588f553bf0c89fd;hb=7b149568c78c6a73915e282ef10edc95171e66fd;hp=c0c0a99c75551b4a3c02c8daf59c1024f8b50804;hpb=029570b7f2633e2b56053c1c51ed140c77dfd26f;p=idzebra-moved-to-github.git

diff --git a/doc/administration.xml b/doc/administration.xml
index c0c0a99..cd0572e 100644
--- a/doc/administration.xml
+++ b/doc/administration.xml
@@ -1,5 +1,5 @@
 <chapter id="administration">
- <!-- $Id: administration.xml,v 1.25 2006-02-16 16:50:18 marc Exp $ -->
+ <!-- $Id: administration.xml,v 1.26 2006-03-04 21:07:57 marc Exp $ -->
  <title>Administrating Zebra</title>
  <!-- ### It's a bit daft that this chapter (which describes half of
           the configuration-file formats) is separated from
@@ -1120,8 +1120,28 @@
      after each update session in order write your changes from the
      shadow to the life register space.
    </para>
+   <para>
+    Extended services are also available from the YAZ client layer. An
+    example of an YAZ-PHP extended service transaction is given here:
+    <screen>
+    <![CDATA[
+     $record = '<record><title>A fine specimen of a record</title></record>';
 
-  
+     $options = array('action' => 'recordInsert',
+                      'syntax' => 'xml',
+                      'record' => $record,
+                      'databaseName' => 'mydatabase'
+                     );
+
+     yaz_es($yaz, 'update', $options);
+     yaz_es($yaz, 'commit', array());
+     yaz_wait();
+
+     if ($error = yaz_error($yaz))
+       echo "$error";
+     ]]>
+    </screen>  
+   </para>
  </sect1>