Ignore:
Timestamp:
Jun 1, 2010, 11:11:30 PM (9 years ago)
Author:
rme
Message:

Remove claims that UDP sockets can use strings as buffers for
sending/receiving.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/source/doc/src/sockets.xml

    r8981 r13774  
    165165                :stream sockets are currently always bivalent (i.e. they
    166166                support both character and byte I/O). For :datagram sockets,
    167                 the format determines the type of buffer created by
    168                 receive-from.</para>
     167                this argument is ignored (the format of a datagram socket
     168                is always :binary).
     169                </para>
    169170              </listitem>
    170171            </varlistentry>
     
    700701
    701702              <listitem>
    702                 <para>If specified, must be either a string or a byte vector
     703                <para>If specified, must be an octet vector
    703704                which will be used to read in the data. If not specified, a
    704705                new buffer will be created (of type determined by
     
    788789              <listitem>
    789790                <para>A vector containing the data to send. It must be
    790                 either a string or a byte vector (either one is acceptable
    791                 regardless of the stream format).</para>
     791                an octet vector.</para>
    792792              </listitem>
    793793            </varlistentry>
     
    797797
    798798              <listitem>
    799                 <para>Number of bytes to send</para>
     799                <para>Number of octets to send</para>
    800800              </listitem>
    801801            </varlistentry>
Note: See TracChangeset for help on using the changeset viewer.