--- sa.pod 2002/10/25 20:45:43 1.30
+++ sa.pod 2002/10/26 15:45:32 1.31
@@ -64,22 +64,22 @@
=item B<Socket Object Operations>:
sa_create,
-sa_destroy.
+sa_destroy.
=item B<Socket Parameter Operations>:
sa_type,
sa_timeout,
-sa_buffer,
-sa_option,
-sa_syscall.
+sa_buffer,
+sa_option,
+sa_syscall.
=item B<Socket Connection Operations>:
sa_bind,
sa_connect,
sa_listen,
-sa_accept,
+sa_accept,
sa_getremote,
sa_getlocal,
sa_shutdown.
@@ -91,7 +91,7 @@
sa_readln,
sa_write,
sa_writef,
-sa_flush.
+sa_flush.
=item B<Socket Input/Output Operations (Datagram Communication)>:
@@ -204,7 +204,7 @@
=item B<sa_addr_t> (Socket Address Abstraction Type)
-This is an opaque data type representing a socket address.
+This is an opaque data type representing a socket address.
Only pointers to this abstract data type are used in the API.
=item B<sa_t> (Socket Abstraction Type)
@@ -237,7 +237,7 @@
=item C<sa_rc_t >B<sa_addr_create>C<(sa_addr_t **>I<saa>C<);>
-Create a socket address abstraction object.
+Create a socket address abstraction object.
The object is stored in I<saa> on success.
Example: C<sa_addr_t *saa; sa_addr_create(&saa);>
@@ -261,7 +261,7 @@
=item C<sa_rc_t >B<sa_addr_u2a>C<(sa_addr_t *>I<saa>C<, const char *>I<uri>C<, ...);>
Import an address into by converting from an URI specification to the
-corresponding address abstraction.
+corresponding address abstraction.
The supported syntax for I<uri> is: "C<unix:>I<path>" for I<Unix Domain>
addresses and "C<inet://>I<addr>C<:>I<port>[C<#>I<protocol>]" for
@@ -298,7 +298,7 @@
=item C<sa_rc_t >B<sa_addr_a2u>C<(sa_addr_t *>I<saa>C<, char **>I<uri>C<);>
Export an address by converting from the address abstraction to the
-corresponding URI specification.
+corresponding URI specification.
The result is a string of the form "C<unix:>I<path>" for I<Unix
Domain> addresses and "C<inet://>I<addr>C<:>I<port>" for I<Internet
@@ -315,7 +315,7 @@
=item C<sa_rc_t >B<sa_addr_a2s>C<(sa_addr_t *>I<saa>C<, struct sockaddr **>I<sabuf>C<, socklen_t *>I<salen>C<);>
Export an address by converting from the address abstraction to the
-corresponding traditional C<struct sockaddr> object.
+corresponding traditional C<struct sockaddr> object.
The result is one of the following particular underlying address
structures: C<struct sockaddr_un> (C<AF_LOCAL>), C<struct sockaddr_in>
@@ -498,7 +498,7 @@
to pass the call through to the replaced actual system call or not.
Possible values for I<id> are (expected prototypes behind I<fptr> are
-given in parenthesis):
+given in parenthesis):
C<SA_SYSCALL_CONNECT>: "C<int (*)([void *,] int, const struct sockaddr
*, socklen_t)>", see connect(2).
@@ -521,20 +521,20 @@
C<SA_SYSCALL_SENDTO>: "C<ssize_t (*)([void *,] int, const void *,
size_t, int, const struct sockaddr *, socklen_t)>", see sendto(2).
-Example:
+Example:
FILE *trace_fp = ...;
- ssize_t
+ ssize_t
trace_read(void *ctx, int fd, void *buf, size_t len)
{
- FILE *fp = (FILE *)ctx;
+ FILE *fp = (FILE *)ctx;
ssize_t rv;
int errno_saved;
rv = read(fd, buf, len);
errno_saved = errno;
- fprintf(fp, "read(%d, %lx, %d) = %d\n",
+ fprintf(fp, "read(%d, %lx, %d) = %d\n",
fd, (long)buf, len, rv);
errno = errno_saved;
return rv;
@@ -602,7 +602,7 @@
are present on the queue, it blocks the caller until a connection is
present.
-Example:
+Example:
sa_addr_t *clt_saa;
sa_t *clt_sa;
@@ -710,7 +710,7 @@
=head2 Standards
R. Gilligan, S. Thomson, J. Bound, W. Stevens:
-"Basic Socket Interface Extensions for IPv6",
+"Basic Socket Interface Extensions for IPv6",
RFC 2553, March 1999.
W. Stevens:
@@ -718,15 +718,15 @@
B<RFC 2292>, February 1998.
R. Fielding, L. Masinter, T. Berners-Lee:
-"Uniform Resource Identifiers: Generic Syntax",
+"Uniform Resource Identifiers: Generic Syntax",
B<RFC 2396>, August 1998.
R. Hinden, S. Deering:
"IP Version 6 Addressing Architecture",
B<RFC 2373>, July 1998.
-R. Hinden, B. Carpenter, L. Masinter:
-"Format for Literal IPv6 Addresses in URL's",
+R. Hinden, B. Carpenter, L. Masinter:
+"Format for Literal IPv6 Addresses in URL's",
B<RFC 2732>, December 1999.
=head2 Papers
@@ -747,21 +747,21 @@
=head2 Manual Pages
socket(2)
-accept(2),
-bind(2),
-connect(2),
-getpeername(2),
+accept(2),
+bind(2),
+connect(2),
+getpeername(2),
getsockname(2),
-getsockopt(2),
-ioctl(2),
-listen(2),
-read(2),
-recv(2),
+getsockopt(2),
+ioctl(2),
+listen(2),
+read(2),
+recv(2),
select(2),
send(2),
-shutdown(2),
-socketpair(2),
-write(2),
+shutdown(2),
+socketpair(2),
+write(2),
getprotoent(3),
protocols(4)
|
