Index of types


A
action [Ftp_client.Action]

C
cmd [Ftp_client]
An FTP command.
cmd_state [Ftp_client]
The command state: `Init: Just connected, no greeting message arrived yet, `Success: Got the greeting message/last command was successful, `Proto_error: currently unused, `Temp_failure: Last command was not successful, and the code was between 400 and 499, `Perm_failure: Last command was not successful, and the code was between 500 and 599, `Rename_seq: Used instead of `Success after the RNFR command, `Restart_seq: Used instead of `Success after the REST command, `User_pass_seq: Used instead of `Success after the USER command when a password must be typed in, `User_acct_seq: Used instead of `Success after the USER command when an account ID must be typed in, `Pass_acct_seq: Used instead of `Success after the PASS command when an account iD must be typed in, `Preliminary: a reply with code 100 to 199. There will be another final reply for the command
connection_cache [Http_client]

D
descr_state [Ftp_data_endpoint]
Describes the state of the socket used for data transfers.

F
filename [Ftp_client]
There are several methods how to specify filenames: `NVFS name: The "Network Virtual File System" is the normal way of accessing FTP files. The client walks into the directory containing the file using CWD and CDUP commands, and calls the file operation from this directory. For simplicity, this client interprets slashes in name as path component separators. The FTP server will never see these slashes., `Verbatim name: The string name is passed to the server without transforming it in any way. In the future, there will be a third way of referring to files: TVFS, the "Trivial Virtual File System".
form_code [Ftp_client]
The form_code has a meaning when FTP is used to print files: `Non_print: This is not the case., `Telnet: Telnet control codes are used for vertical movement, `ASA: ASA (Fortran) control codes are used for vertical movement
ftp_state [Ftp_client]
The ftp_state reflects the knowledge of the client about what has been agreed upon with the server.

H
header_kind [Http_client]
The `Base header is set by the user of http_call and is never changed during processing the call.
how_to_reconnect [Http_client]
How to deal with automatic reconnections, especially when the connection crashes.
how_to_redirect [Http_client]
http_options [Http_client]
Options for the whole pipeline

L
local_receiver [Ftp_data_endpoint]
The local_receiver is the object that gets the data received over the data connection.
local_sender [Ftp_data_endpoint]
The local_sender is the object that provides the data sent over the data connection.

P
plan [Ftp_client.Action]
port [Ftp_client]
The port of the data connection: `Active means that the server initiates the data connection to the listening client, and in the case of `Passive the client initiates the data connection to the listening server.
private_api [Http_client]
The private part of the http_call class type

R
reply [Ftp_client]
Reply code plus text
representation [Ftp_client]
The representation of the transferred file: `ASCII: An ASCII variant is used, i.e. the server sends files in ASCII encoding with CR/LF as end-of-line marker. Supported by all servers., `EBCDIC: An EBCDIC variant is used, i.e. the server sends files in EBCDIC encoding with NEL as end-of-line marker, `Image: The file is transferred in its original binary representation. Supported by all servers. "Local" representations are not supported.
resolver [Http_client]
A name resolver is a function r called as r esys name reply.
response_body_storage [Http_client]
How to create the response body: `Memory: The response body is in-memory, `File f: The response body is stored into the file whose name is returned by f(), `Body f: The response body is stored into the object returned by f()

S
status [Http_client]
Condensed status information of a HTTP call: `Unserved: The call has not yet been finished, `HTTP_protocol_error e: An error on HTTP level occurred. Corresponds to the exception Http_protocol., `Successful: The call is successful, and the response code is between 200 and 299., `Redirection: The call is successful, and the response code is between 300 and 399., `Client_error: The call failed with a response code between 400 and 499., `Server_error: The call failed for any other reason.
structure [Ftp_client]
The client supports two structures: `File_structure: Files are simply contiguous streams of bytes, `Record_structure: Files are sequences of records. FTP does not make a difference between variable and fixed length records. It is not forbidden that the records are themselves structured into lines, in fact it can happen that end-of-line markers are contained in binary records. Operating systems that support record-structured files often store text files in this format, i.e. every line is stored in its own record, without end-of-line marker. If record structure is selected by a STRU command, it is recommended to use the classes Ftp_data_endpoint.out_record_channel and Ftp_data_endpoint.in_record_channel for the local representation of the files, otherwise the records may be incorrectly mapped to the local conventions. Page-structured files (i.e.
synchronization [Http_client]
This type determines whether to keep requests and responses synchronized or not.

T
telnet_command [Telnet_client]
A telnet_command is the interpretation of the octets in a Telnet session, i.e.
telnet_connector [Telnet_client]
Connectors: Telnet_connect(host,port): The client connects to this port., Telnet_socket s: The client uses an already connected socket. Why Telnet_socket? Telnet is a symmetrical protocol; client and servers implement the same protocol features (the only difference is the environment: a client is typically connected with a real terminal; a server is connected with a pseudo terminal).
telnet_negotiated_option [Telnet_client]
telnet_negotiated_option: names for the most common options, and the generic name Telnet_option for other options.
telnet_option_state [Telnet_client]
An option has one of three states: Not_negotiated: There was no negotiation about the option. This means that the option is turned off (but this client is allowed to reject it explicitly), Accepted: Both sides have accepted the option., Rejected: One side has rejected the option. This also means that the option is off, but the client refuses to send further acknoledgements that the option is off (to avoid endless negotiation loops).
telnet_options [Telnet_client]
telnet_options: modifies the behaviour of the client.
text_data_repr [Ftp_data_endpoint]
Possible representation of text data: `ASCII means an ASCII-compatible encoding where the newline character is represented by CR/LF.
transmission_mode [Ftp_data_endpoint]
The transmission mode as described in RFC 959.
transmission_mode [Ftp_client]
The transmission mode selects how the data are encoded in the data connection.