/usr/share/doc/refdb/refdb-manual/ch23.html is in refdb-doc 1.0.2-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 23. The RefDB client/server communication protocol</title><link rel="stylesheet" type="text/css" href="manual.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /><link rel="home" href="index.html" title="RefDB handbook" /><link rel="up" href="pt05.html" title="Part V. Programmer's manual" /><link rel="prev" href="ch22s04.html" title="Processing expectations for the RefDB DocBook bibliography output" /><link rel="next" href="ch23s02.html" title="Basic principles" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 23. The RefDB client/server communication protocol</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch22s04.html">Prev</a> </td><th width="60%" align="center">Part V. Programmer's manual</th><td width="20%" align="right"> <a accesskey="n" href="ch23s02.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h2 class="title"><a id="chapter-cs-protocol"></a>Chapter 23. The RefDB client/server communication protocol</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="sect1"><a href="ch23.html#idp71235616">Prerequisites</a></span></dt><dt><span class="sect1"><a href="ch23s02.html">Basic principles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch23s02.html#idp71232848">Message format</a></span></dt><dt><span class="sect2"><a href="ch23s02.html#idp75600480">First stage</a></span></dt><dt><span class="sect2"><a href="ch23s02.html#idp75583296">Second stage</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch23s03.html">Commented abstract representation of the client/server protocol</a></span></dt><dd><dl><dt><span class="sect2"><a href="ch23s03.html#idp75627232">First stage</a></span></dt><dt><span class="sect2"><a href="ch23s03.html#idp75652352">Second stage</a></span></dt><dt><span class="sect2"><a href="ch23s03.html#sect-statusmessages">Status messages</a></span></dt></dl></dd><dt><span class="sect1"><a href="ch23s04.html">Tools for the client-server protocol</a></span></dt><dd><dl><dt><span class="refentry"><a href="re30.html">eenc</a></span></dt><dd><dl><dt><span class="refsect1"><a href="re30.html#eenc-description">Description</a></span></dt><dt><span class="refsect1"><a href="re30.html#eenc-options">Options</a></span></dt><dt><span class="refsect1"><a href="re30.html#eenc-see_also">See also</a></span></dt><dt><span class="refsect1"><a href="re30.html#eenc-author">Author</a></span></dt></dl></dd></dl></dd></dl></div><p>This chapter describes the communication protocol that the RefDB clients and server use to talk to each other. Knowledge of this protocol is useful for programmers who want to write custom RefDB clients. The protocol is versioned in order to allow clients and servers to negotiate whether they can fulfil each other's expectations. The protocol described in this document is version 5.</p><div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Tip</h3><p>The RefDB project provides a Perl client module in addition to the C clients shipped with the RefDB package proper. Due to the simplicity of the Perl language, this module is a good resource for programmers who want to implement clients in other programming languages.</p></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="idp71235616"></a>Prerequisites</h2></div></div></div><p>Custom clients or client libraries can be implemented in any programming language that can create a Unix socket connection to the server and send/receive byte sequences through the socket. As the transferred data are essentially plain text, the endianness of the computer as well as the internal representation of data types in the particular programming language are irrelevant.</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch22s04.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="pt05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch23s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Processing expectations for the RefDB DocBook bibliography output </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Basic principles</td></tr></table></div></body></html>
|