← Back to branch summary

~ubuntu-branches/debian/stretch/libnice/stretch

« back to all changes in this revision

Viewing changes to docs/reference/libnice/xml/stunmessage.xml

  • Committer: Bazaar Package Importer
  • Author(s): Laurent Bigonville
  • Date: 2009-11-13 22:53:11 UTC
  • mfrom: (1.2.3 upstream) (5.1.4 sid)
  • Revision ID: james.westby@ubuntu.com-20091113225311-42r7p09nkxk9313k
Tags: 0.0.10-2
Disable check on non-linux arch for now as they are buggy on these arch

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/reference/libnice/xml/stunmessage.xml
653
653
</variablelist></refsect2>
654
654
<refsect2 id="StunTransactionId" role="typedef">
655
655
<title>StunTransactionId</title>
656
 
<indexterm zone="StunTransactionId"><primary sortas="StunTransactionId">StunTransactionId</primary></indexterm><para>
 
656
<indexterm zone="StunTransactionId"><primary sortas="StunTransactionId">StunTransactionId</primary></indexterm><programlisting>typedef uint8_t StunTransactionId[STUN_MESSAGE_TRANS_ID_LEN];
 
657
</programlisting>
 
658
<para>
657
659
A type that holds a STUN transaction id.</para>
658
660
<para>
659
661
</para></refsect2>
856
858
</variablelist></refsect2>
857
859
<refsect2 id="STUN-MESSAGE-BUFFER-INCOMPLETE--CAPS" role="macro">
858
860
<title>STUN_MESSAGE_BUFFER_INCOMPLETE</title>
859
 
<indexterm zone="STUN-MESSAGE-BUFFER-INCOMPLETE--CAPS"><primary sortas="STUN_MESSAGE_BUFFER_INCOMPLETE">STUN_MESSAGE_BUFFER_INCOMPLETE</primary></indexterm><programlisting>#define             STUN_MESSAGE_BUFFER_INCOMPLETE</programlisting>
 
861
<indexterm zone="STUN-MESSAGE-BUFFER-INCOMPLETE--CAPS"><primary sortas="STUN_MESSAGE_BUFFER_INCOMPLETE">STUN_MESSAGE_BUFFER_INCOMPLETE</primary></indexterm><programlisting>#define STUN_MESSAGE_BUFFER_INCOMPLETE 0
 
862
</programlisting>
860
863
<para>
861
864
Convenience macro for <link linkend="stun-message-validate-buffer-length"><function>stun_message_validate_buffer_length()</function></link> meaning that the
862
865
data to validate does not hold a complete STUN message</para>
864
867
</para></refsect2>
865
868
<refsect2 id="STUN-MESSAGE-BUFFER-INVALID--CAPS" role="macro">
866
869
<title>STUN_MESSAGE_BUFFER_INVALID</title>
867
 
<indexterm zone="STUN-MESSAGE-BUFFER-INVALID--CAPS"><primary sortas="STUN_MESSAGE_BUFFER_INVALID">STUN_MESSAGE_BUFFER_INVALID</primary></indexterm><programlisting>#define             STUN_MESSAGE_BUFFER_INVALID</programlisting>
 
870
<indexterm zone="STUN-MESSAGE-BUFFER-INVALID--CAPS"><primary sortas="STUN_MESSAGE_BUFFER_INVALID">STUN_MESSAGE_BUFFER_INVALID</primary></indexterm><programlisting>#define STUN_MESSAGE_BUFFER_INVALID -1
 
871
</programlisting>
868
872
<para>
869
873
Convenience macro for <link linkend="stun-message-validate-buffer-length"><function>stun_message_validate_buffer_length()</function></link> meaning that the
870
874
data to validate is not a valid STUN message</para>