doc: Fix order of protocol messages in listing

Move GSSENCRequest to the correct alphabetical position.
pull/57/head
Peter Eisentraut 5 years ago
parent 2f0760c9ff
commit 8fed2eadb8
  1. 75
      doc/src/sgml/protocol.sgml

@ -4858,6 +4858,44 @@ FunctionCallResponse (B)
</varlistentry>
<varlistentry>
<term>
GSSENCRequest (F)
</term>
<listitem>
<para>
<variablelist>
<varlistentry>
<term>
Int32(8)
</term>
<listitem>
<para>
Length of message contents in bytes, including self.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
Int32(80877104)
</term>
<listitem>
<para>
The <acronym>GSSAPI</acronym> Encryption request code. The value is chosen to contain
<literal>1234</literal> in the most significant 16 bits, and <literal>5680</literal> in the
least significant 16 bits. (To avoid confusion, this code
must not be the same as any protocol version number.)
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
GSSResponse (F)
@ -5823,43 +5861,6 @@ SSLRequest (F)
</listitem>
</varlistentry>
<varlistentry>
<term>
GSSENCRequest (F)
</term>
<listitem>
<para>
<variablelist>
<varlistentry>
<term>
Int32(8)
</term>
<listitem>
<para>
Length of message contents in bytes, including self.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>
Int32(80877104)
</term>
<listitem>
<para>
The <acronym>GSSAPI</acronym> Encryption request code. The value is chosen to contain
<literal>1234</literal> in the most significant 16 bits, and <literal>5680</literal> in the
least significant 16 bits. (To avoid confusion, this code
must not be the same as any protocol version number.)
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>

Loading…
Cancel
Save