From dbf9c223cf7efd8fc6143b573fcc12637d5ae9ae Mon Sep 17 00:00:00 2001
From: Micael Karlberg This module provides the Erlang Webserver API programmer with
- utility functions for adding run-time configuration directives.
This module provides the Erlang Web server API module programmer
- with utility functions for generic sockets communication. The
- appropriate communication mechanism is transparently used, that
- is
Erlang Webserver Server internal API for handling of things - such as interaction data exported by the mod_alias module.
+ such as interaction data exported by the mod_alias module. + +If
This module provides for basic user authentication using - textual files, dets databases as well as mnesia databases.
+ textual files, dets databases as well as mnesia databases. + +Starts a daemon process which listens for udp packets on a - port. When it receives a request for read or write it spawns - a temporary server process which handles the actual transfer - of the (virtual) file.
+ port. When it receives a request for read or write it spawns + a temporary server process which handles the actual transfer + of the (virtual) file. + +Reads a (virtual) file
If
If
If
If
If
If
If
Returns info about all TFTP daemon processes. -
+Returns info about all TFTP daemon processes.
+ +Returns info about all TFTP server processes. -
+Returns info about all TFTP server processes.
+ +Returns info about a TFTP daemon, server or client process.
+ +Changes config for all TFTP daemon processes -
+Changes config for all TFTP daemon processes.
+ +Changes config for all TFTP server processes -
+Changes config for all TFTP server processes.
+ +Changes config for a TFTP daemon, server or client process
+ +Prepares to open a file on the client side.
-No new options may be added, but the ones that are present in
-
Will be followed by a call to
Prepares to open a file on the client side.
+No new options may be added, but the ones that are present in
+
Will be followed by a call to
Opens a file for read or write access.
On the client side where the
On the server side, where there is no preceding
-
On the server side, where there is no preceding
+
Read a chunk from the file.
The callback function is expected to close - the file when the last file chunk is - encountered. When an error is encountered - the callback function is expected to clean - up after the aborted file transfer, such as - closing open file descriptors etc. In both - cases there will be no more calls to any of - the callback functions.
+ the file when the last file chunk is + encountered. When an error is encountered + the callback function is expected to clean + up after the aborted file transfer, such as + closing open file descriptors etc. In both + cases there will be no more calls to any of + the callback functions. + +Write a chunk to the file.
The callback function is expected to close - the file when the last file chunk is - encountered. When an error is encountered - the callback function is expected to clean - up after the aborted file transfer, such as - closing open file descriptors etc. In both - cases there will be no more calls to any of - the callback functions.
+ the file when the last file chunk is + encountered. When an error is encountered + the callback function is expected to clean + up after the aborted file transfer, such as + closing open file descriptors etc. In both + cases there will be no more calls to any of + the callback functions. + +Invoked when the file transfer is aborted.
The callback function is expected to clean - up its used resources after the aborted file - transfer, such as closing open file - descriptors etc. The function will not be - invoked if any of the other callback - functions returns an error, as it is - expected that they already have cleaned up - the necessary resources. It will however be - invoked if the functions fails (crashes).
+ up its used resources after the aborted file + transfer, such as closing open file + descriptors etc. The function will not be + invoked if any of the other callback + functions returns an error, as it is + expected that they already have cleaned up + the necessary resources. It will however be + invoked if the functions fails (crashes).A
Log an error message. See
Log an error message.
+ See
Log a warning message. See
Log a warning message.
+ See
Log an info message. See
Log an info message.
+ See