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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- This document was generated using DocBuilder 3.3.3 -->
<HTML>
<HEAD>
<TITLE>Introduction</TITLE>
<SCRIPT type="text/javascript" src="../../../../doc/erlresolvelinks.js">
</SCRIPT>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#FF00FF"
ALINK="#FF0000">
<CENTER>
<A HREF="http://www.erlang.se"><IMG BORDER=0 ALT="[Ericsson AB]" SRC="min_head.gif"></A>
</CENTER>
<A NAME="1"><!-- Empty --></A>
<H2>1 Introduction</H2>
<A NAME="1.1"><!-- Empty --></A>
<H3>1.1 Purpose</H3>
<P> Inets is a container for Internet clients and servers. Currently, an
<A HREF="part_term.html#HTTP">HTTP</A> server, a FTP client and an HTTP client has
been incorporated into Inets. The HTTP server and client is
HTTP 1.1 compliant as defined in <A HREF="part_term.html#RFC">RFC</A> 2616.
<P> The HTTP client is now documented <A HREF="http.html">http(3)</A> and supported. It is loosely
based on the earlier unsupported client developed by Johan Blom
of Mobile Arts AB.
<A NAME="1.2"><!-- Empty --></A>
<H3>1.2 Prerequisites</H3>
<P>It is assumed that the reader is familiar with the Erlang
programming language, concepts of OTP and has a basic
understanding of the HTTP and FTP protocols.<A NAME="1.3"><!-- Empty --></A>
<H3>1.3 The Service Concept</H3>
<P> Each client and server in inets is viewed as service. When
starting the inets application the inets top supervisor will
start a number of subsupervisors and worker processes for
handling the different services provided. Some services require
that there exist a configuration file, such as HTTP server(s),
in order for the service(s) to be started. While the HTTP
clients main process always will be started (it remains idle
until some process issues a request) in this case the
configuration is optional. Other services may not be
configurable and have a more dynamic character, such as ftp
clients, that will add worker processes to the supervision tree
every time you do ftp:open/[1,2,3] an remove them every time you
do ftp:close/1.
<P>Services that needs configuring should be put into the inets
applications configuration file on the form:
<PRE>
[{inets, [{services, ListofConfiguredServices}]}].
</PRE>
<P>For details of exactly what to put in the list of configured
services see the documentation for the services that needs
configuring.<CENTER>
<HR>
<SMALL>
Copyright © 1991-2006
<A HREF="http://www.erlang.se">Ericsson AB</A><BR>
</SMALL>
</CENTER>
</BODY>
</HTML>
|
