aboutsummaryrefslogtreecommitdiffstats
path: root/lib/inets/doc/src/ftp_client.xml
blob: 2f5b8abb5f28c001fb73a0794a86d6e832b05f0d (plain) (blame)
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
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>
  <header>
    <copyright>
      <year>2004</year><year>2013</year>
      <holder>Ericsson AB. All Rights Reserved.</holder>
    </copyright>
    <legalnotice>
      Licensed under the Apache License, Version 2.0 (the "License");
      you may not use this file except in compliance with the License.
      You may obtain a copy of the License at
 
          http://www.apache.org/licenses/LICENSE-2.0

      Unless required by applicable law or agreed to in writing, software
      distributed under the License is distributed on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      See the License for the specific language governing permissions and
      limitations under the License.
    
    </legalnotice>

    <title>FTP Client</title>
    <prepared>Ingela Anderton Andin</prepared>
    <responsible></responsible>
    <docno></docno>
    <approved></approved>
    <checked></checked>
    <date></date>
    <rev></rev>
    <file>ftp_client.xml</file>
  </header>

  <section>
    <title>Introduction</title>

    <p>Ftp clients are consider to be rather temporary and are
      for that reason only started and stopped during
      runtime and can not be started at application startup.
      Due to the design of FTP client API, letting some
      functions return intermediate results, only the process
      that started the ftp client will be able to access it in
      order to preserve sane semantics. (This could be solved
      by changing the API and using the concept of a controlling
      process more in line with other OTP applications, but
      that is perhaps something for the future.) 
      If the process that started the ftp session 
      dies the ftp client process will terminate.</p>

    <p>The client supports ipv6 as long as the underlying mechanisms
      also do so. </p>

    </section>

  <section>
    <title>Using the FTP Client API</title>
    <p>The following is a simple example of an ftp session, where
      the user <c>guest</c> with password <c>password</c> logs on to
      the remote host <c>erlang.org</c>, and where the file
      <c>appl.erl</c> is transferred from the remote to the local
      host.  When the session is opened, the current directory at
      the remote host is <c>/home/guest</c>, and <c>/home/fred</c>
      at the local host. Before transferring the file, the current
      local directory is changed to <c>/home/eproj/examples</c>, and
      the remote directory is set to
      <c>/home/guest/appl/examples</c>.</p>
    <code type="erl"><![CDATA[
      1> inets:start().
      ok
      2> {ok, Pid} = inets:start(ftpc, [{host, "erlang.org"}]).
      {ok,<0.22.0>}
      3> ftp:user(Pid, "guest", "password").
      ok
      4> ftp:pwd(Pid).
      {ok, "/home/guest"}
      5> ftp:cd(Pid, "appl/examples").
      ok
      6> ftp:lpwd(Pid).
      {ok, "/home/fred"}.
      7> ftp:lcd(Pid, "/home/eproj/examples").
      ok
      8> ftp:recv(Pid, "appl.erl").
      ok
      9> inets:stop(ftpc, Pid).
      ok
    ]]></code>
  </section>
</chapter>