From c54168c72bb42f8ffb0e341fd56cd81a89b53430 Mon Sep 17 00:00:00 2001
From: tmanevik 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. FTP clients are considered to be rather temporary. Thus,
+ they are only started and stopped during runtime and cannot
+ be started at application startup.
+ The FTP client API is designed to allow some functions to
+ return intermediate results. This implies that only the process
+ that started the FTP client can access it with
+ preserved sane semantics. (This can be solved
+ by changing the API, using the concept of a controlling
+ process as with other OTP applications, but
+ that is something for future releases of The client supports ipv6 as long as the underlying mechanisms
- also do so. The client supports IPv6 as long as the underlying mechanisms
+ also do so. The following is a simple example of an ftp session, where
+ The following is a simple example of an FTP session, where
the user
inets:start().
ok
@@ -86,6 +75,14 @@
9> inets:stop(ftpc, Pid).
ok
]]>
+ The file
+