1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.11 $ -->
<refentry xmlns="http://docbook.org/ns/docbook" xml:id="function.socket-create">
<refnamediv>
<refname>socket_create</refname>
<refpurpose>Create a socket (endpoint for communication)</refpurpose>
</refnamediv>
<refsect1 role="description">
&reftitle.description;
<methodsynopsis>
<type>resource</type><methodname>socket_create</methodname>
<methodparam><type>int</type><parameter>domain</parameter></methodparam>
<methodparam><type>int</type><parameter>type</parameter></methodparam>
<methodparam><type>int</type><parameter>protocol</parameter></methodparam>
</methodsynopsis>
<para>
Creates and returns a socket resource, also referred to as an endpoint
of communication. A typical network connection is made up of 2 sockets, one
performing the role of the client, and another performing the role of the server.
</para>
</refsect1>
<refsect1 role="parameters">
&reftitle.parameters;
<para>
<variablelist>
<varlistentry>
<term><parameter>domain</parameter></term>
<listitem>
<para>
The <parameter>domain</parameter> parameter specifies the protocol
family to be used by the socket.
</para>
<table>
<title>Available address/protocol families</title>
<tgroup cols="2">
<thead>
<row>
<entry>Domain</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>AF_INET</entry>
<entry>
IPv4 Internet based protocols. TCP and UDP are common protocols of
this protocol family.
</entry>
</row>
<row>
<entry>AF_INET6</entry>
<entry>
IPv6 Internet based protocols. TCP and UDP are common protocols of
this protocol family. Support added in PHP 5.0.0.
</entry>
</row>
<row>
<entry>AF_UNIX</entry>
<entry>
Local communication protocol family. High efficiency and low
overhead make it a great form of IPC (Interprocess Communication).
</entry>
</row>
</tbody>
</tgroup>
</table>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>type</parameter></term>
<listitem>
<para>
The <parameter>type</parameter> parameter selects the type of communication
to be used by the socket.
</para>
<table>
<title>Available socket types</title>
<tgroup cols="2">
<thead>
<row>
<entry>Type</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>SOCK_STREAM</entry>
<entry>
Provides sequenced, reliable, full-duplex, connection-based byte streams.
An out-of-band data transmission mechanism may be supported.
The TCP protocol is based on this socket type.
</entry>
</row>
<row>
<entry>SOCK_DGRAM</entry>
<entry>
Supports datagrams (connectionless, unreliable messages of a fixed maximum length).
The UDP protocol is based on this socket type.
</entry>
</row>
<row>
<entry>SOCK_SEQPACKET</entry>
<entry>
Provides a sequenced, reliable, two-way connection-based data transmission path for
datagrams of fixed maximum length; a consumer is required to read an
entire packet with each read call.
</entry>
</row>
<row>
<entry>SOCK_RAW</entry>
<entry>
Provides raw network protocol access. This special type of socket
can be used to manually construct any type of protocol. A common use
for this socket type is to perform ICMP requests (like ping,
traceroute, etc).
</entry>
</row>
<row>
<entry>SOCK_RDM</entry>
<entry>
Provides a reliable datagram layer that does not guarantee ordering.
This is most likely not implemented on your operating system.
</entry>
</row>
</tbody>
</tgroup>
</table>
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>protocol</parameter></term>
<listitem>
<para>
The <parameter>protocol</parameter> parameter sets the specific
protocol within the specified <parameter>domain</parameter> to be used
when communicating on the returned socket. The proper value can be
retrieved by name by using <function>getprotobyname</function>. If
the desired protocol is TCP, or UDP the corresponding constants
<constant>SOL_TCP</constant>, and <constant>SOL_UDP</constant>
can also be used.
</para>
<table>
<title>Common protocols</title>
<tgroup cols="2">
<thead>
<row>
<entry>Name</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry>icmp</entry>
<entry>
The Internet Control Message Protocol is used primarily by gateways
and hosts to report errors in datagram communication. The "ping"
command (present in most modern operating systems) is an example
application of ICMP.
</entry>
</row>
<row>
<entry>udp</entry>
<entry>
The User Datagram Protocol is a connectionless, unreliable,
protocol with fixed record lengths. Due to these aspects, UDP
requires a minimum amount of protocol overhead.
</entry>
</row>
<row>
<entry>tcp</entry>
<entry>
The Transmission Control Protocol is a reliable, connection based,
stream oriented, full duplex protocol. TCP guarantees that all data packets
will be received in the order in which they were sent. If any packet is somehow
lost during communication, TCP will automatically retransmit the packet until
the destination host acknowledges that packet. For reliability and performance
reasons, the TCP implementation itself decides the appropriate octet boundaries
of the underlying datagram communication layer. Therefore, TCP applications must
allow for the possibility of partial record transmission.
</entry>
</row>
</tbody>
</tgroup>
</table>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect1>
<refsect1 role="returnvalues">
&reftitle.returnvalues;
<para>
<function>socket_create</function> returns a socket resource on success,
or &false; on error. The actual error code can be retrieved by calling
<function>socket_last_error</function>. This error code may be passed to
<function>socket_strerror</function> to get a textual explanation of the
error.
</para>
</refsect1>
<refsect1 role="errors">
&reftitle.errors;
<para>
If an invalid <parameter>domain</parameter> or
<parameter>type</parameter> is given, <function>socket_create</function>
defaults to <constant>AF_INET</constant> and
<constant>SOCK_STREAM</constant> respectively and additionally emits an
<constant>E_WARNING</constant> message.
</para>
</refsect1>
<refsect1 role="seealso">
&reftitle.seealso;
<para>
<simplelist>
<member><function>socket_accept</function></member>
<member><function>socket_bind</function></member>
<member><function>socket_connect</function></member>
<member><function>socket_listen</function></member>
<member><function>socket_last_error</function></member>
<member><function>socket_strerror</function></member>
</simplelist>
</para>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->
|
