107 lines
6.8 KiB
HTML
107 lines
6.8 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Create a connectionless socket" />
|
||
|
|
<meta name="abstract" content="Connectionless sockets do not establish a connection over which data is transferred. Instead, the server application specifies its name where a client can send requests." />
|
||
|
|
<meta name="description" content="Connectionless sockets do not establish a connection over which data is transferred. Instead, the server application specifies its name where a client can send requests." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="bdesign.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="xconlessserver.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="xconlessclient.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/close.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/socket.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/bind.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/recvfr.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/sendto.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/ghostnm.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="connectionless" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Create a connectionless socket</title>
|
||
|
|
</head>
|
||
|
|
<body id="connectionless"><a name="connectionless"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Create a connectionless socket</h1>
|
||
|
|
<div><p>Connectionless sockets do not establish a connection over which
|
||
|
|
data is transferred. Instead, the server application specifies its name where
|
||
|
|
a client can send requests.</p>
|
||
|
|
<div class="section"><p>Connectionless sockets use User Datagram Protocol (UDP) instead
|
||
|
|
of TCP/IP. </p>
|
||
|
|
<p>The
|
||
|
|
following figure illustrates the client/server relationship from the socket
|
||
|
|
APIs used in the code examples for a connectionless socket design.</p>
|
||
|
|
<br /><img src="rxab6503.gif" alt="The client/server relationship of the socket APIs for a connectionless protocol" /><br /></div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Socket flow of events: Connectionless server</h4><p>The
|
||
|
|
following sequence of the socket calls provide a description of the figure
|
||
|
|
and the following example programs. It also describes the relationship
|
||
|
|
between the server and client application in a connectionless design. Each
|
||
|
|
set of flows contain links to usage notes on specific APIs. If you need more
|
||
|
|
details on the use of a particular API, you can use these links. The first
|
||
|
|
example uses the following sequence of function calls:</p>
|
||
|
|
<ol><li>The <span class="apiname">socket()</span> function returns a socket descriptor representing
|
||
|
|
an endpoint. The statement also identifies that the INET (Internet Protocol)
|
||
|
|
address family with the UDP transport (SOCK_DGRAM) is used for this socket.</li>
|
||
|
|
<li>After the socket descriptor is created, a <span class="apiname">bind()</span> function
|
||
|
|
gets a unique name for the socket. In this example, the user sets the s_addr
|
||
|
|
to zero, which means that the UDP port of 3555 is bound to all IPv4 addresses
|
||
|
|
on the system.</li>
|
||
|
|
<li>The server uses the <span class="apiname">recvfrom()</span> function to receive
|
||
|
|
that data. The <span class="apiname">recvfrom()</span> function waits indefinitely for
|
||
|
|
data to arrive.</li>
|
||
|
|
<li>The <span class="apiname">sendto()</span> function echoes the data back to the client.</li>
|
||
|
|
<li>The <span class="apiname">close()</span> function ends any open socket descriptors.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Socket flow of events: Connectionless client</h4><p>The
|
||
|
|
second example uses the following sequence of function calls:</p>
|
||
|
|
<ol><li>The <span class="apiname">socket()</span> function returns a socket descriptor representing
|
||
|
|
an endpoint. The statement also identifies that the INET (Internet Protocol)
|
||
|
|
address family with the UDP transport (SOCK_DGRAM) is used for this socket.
|
||
|
|
</li>
|
||
|
|
<li>In the client example program, if the server string that was passed into
|
||
|
|
the inet_addr() function was not a dotted decimal IP address, then it is assumed
|
||
|
|
to be the hostname of the server. In that case, use the <span class="apiname">gethostbyname()</span> function
|
||
|
|
to retrieve the IP address of the server.</li>
|
||
|
|
<li>Use the <span class="apiname">sendto()</span> function to send the data to the server. </li>
|
||
|
|
<li>Use the <span class="apiname">recvfrom()</span> function to receive the data back
|
||
|
|
from the server.</li>
|
||
|
|
<li>The <span class="apiname">close()</span> function ends any open socket descriptors. </li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="xconlessserver.htm">Example: A connectionless server</a></strong><br />
|
||
|
|
This example can be used to create your own connectionless server design. This example uses User Datagram Protocol (UDP) to create a connectionless socket server program.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="xconlessclient.htm">Example: A connectionless client</a></strong><br />
|
||
|
|
This example shows how to use User Datagram Protocol (UDP) to connect a connectionless socket client program to a server.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="bdesign.htm" title="This topic provides examples of sockets programs that use the most basic design.">Basic socket design</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../apis/close.htm">close()</a></div>
|
||
|
|
<div><a href="../apis/socket.htm">socket()</a></div>
|
||
|
|
<div><a href="../apis/bind.htm">bind()</a></div>
|
||
|
|
<div><a href="../apis/recvfr.htm">recvfrom()</a></div>
|
||
|
|
<div><a href="../apis/sendto.htm">sendto()</a></div>
|
||
|
|
<div><a href="../apis/ghostnm.htm">gethostbyname()</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|