106 lines
7.4 KiB
HTML
106 lines
7.4 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Advanced socket concepts" />
|
||
|
|
<meta name="abstract" content="Advanced socket concepts go beyond a general discussion of what sockets are and how they work. They provide ways to design socket applications for larger and more complex networks." />
|
||
|
|
<meta name="description" content="Advanced socket concepts go beyond a general discussion of what sockets are and how they work. They provide ways to design socket applications for larger and more complex networks." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzab6soxoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="asynchi0.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cssl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="csocks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cthread.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cnonblock.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="csignals.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cmulticast.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="ctransfer.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="coobd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cmultiplex.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="routines.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cbsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cunix98.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cdescriptors.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="aconcepts" />
|
||
|
|
<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>Advanced socket concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="aconcepts"><a name="aconcepts"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Advanced socket concepts</h1>
|
||
|
|
<div><p>Advanced socket concepts go beyond a general discussion of what
|
||
|
|
sockets are and how they work. They provide ways to design socket applications
|
||
|
|
for larger and more complex networks.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="asynchi0.htm">Asynchronous I/O</a></strong><br />
|
||
|
|
Asynchronous I/O APIs provide a method for threaded client server models to perform highly concurrent and memory efficient I/O.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cssl.htm">Secure sockets</a></strong><br />
|
||
|
|
Currently, i5/OS™ supports two methods of creating secure socket
|
||
|
|
applications on the iSeries™. The SSL_ APIs and Global Secure Toolkit
|
||
|
|
(GSKit) APIs provide communications privacy over an open communications network,
|
||
|
|
which in most cases is the Internet.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="csocks.htm">Client SOCKS support</a></strong><br />
|
||
|
|
iSeries™ uses
|
||
|
|
SOCKS version 4 to enable programs that use the AF_INET address family with
|
||
|
|
SOCK_STREAM socket type to communicate with server programs that run on systems
|
||
|
|
outside a firewall.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cthread.htm">Thread safety</a></strong><br />
|
||
|
|
A function is considered threadsafe if you can start it simultaneously in multiple threads within the same process.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cnonblock.htm">Nonblocking I/O</a></strong><br />
|
||
|
|
When an application issues one of the socket input functions and there is no data to read, the function blocks and does not return until there is data to read.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="csignals.htm">Signals</a></strong><br />
|
||
|
|
An application program can request to be notified asynchronously
|
||
|
|
(request that the system send a <dfn class="term">signal</dfn>) when a condition that
|
||
|
|
the application is interested in occurs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cmulticast.htm">IP multicasting</a></strong><br />
|
||
|
|
IP multicasting allows an application to send a single IP datagram that a group of hosts in a network can receive.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="ctransfer.htm">File data transfer—send_file() and accept_and_recv()</a></strong><br />
|
||
|
|
i5/OS™ sockets
|
||
|
|
provide the <span class="apiname">send_file()</span> and <span class="apiname">accept_and_recv()</span> APIs
|
||
|
|
that enable faster and easier file transfers over connected sockets.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="coobd.htm">Out-of-band data</a></strong><br />
|
||
|
|
Out-of-band (OOB) data is user-specific data that only has meaning for connection-oriented (stream) sockets.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cmultiplex.htm">I/O multiplexing—select()</a></strong><br />
|
||
|
|
Because asynchronous I/O provides a more efficient way to maximize
|
||
|
|
your application resources, it is recommended that you use asynchronous I/O
|
||
|
|
APIs rather than the <span class="apiname">select()</span> API. However, your specific
|
||
|
|
application design may allow <span class="apiname">select()</span> to be used.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="routines.htm">Socket network functions</a></strong><br />
|
||
|
|
Socket network functions allow application programs to obtain information from the host, protocol, service, and network files.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dns.htm">Domain Name System support</a></strong><br />
|
||
|
|
iSeries™ provides
|
||
|
|
applications with access to the Domain Name System (DNS) through the resolver
|
||
|
|
functions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cbsd.htm">Berkeley Software Distribution compatibility</a></strong><br />
|
||
|
|
Sockets is a Berkeley Software Distribution (BSD) interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cunix98.htm">UNIX 98 compatibility</a></strong><br />
|
||
|
|
Created by The Open Group, a consortium of developers and venders, UNIX<sup>®</sup> 98
|
||
|
|
improved the inter-operability of the UNIX<sup>®</sup> operating system while incorporating
|
||
|
|
much of the Internet-related function for which UNIX<sup>®</sup> had become known.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="cdescriptors.htm">Descriptor passing between processes—sendmsg() and recvmsg()</a></strong><br />
|
||
|
|
The ability to pass an open descriptor between jobs can lead to a new way of designing client/server applications.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzab6soxoverview.htm" title="A socket is a communications connection point (endpoint) that you can name and address in a network.">Socket programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|