| A | |
| async_in_channel [Uq_engines] | 
An asynchrounous input channel provides methods to input data from
 a stream descriptor.
 | 
| async_in_channel_engine [Uq_engines] | 
Combination of engine + async_in_channel
 | 
| async_out_channel [Uq_engines] | 
An asynchrounous output channel provides methods to output data to
 a stream descriptor.
 | 
| async_out_channel_engine [Uq_engines] | 
Combination of engine + async_out_channel
 | 
| auth_handler [Http_client] | 
An authentication handler has the capability of adding the necessary
 headers to messages.
 | 
| auth_method [Rpc_server] | |
| auth_method [Rpc_client] | 
An  auth_methodobject represents a method of authentication. | 
| auth_session [Rpc_client] | 
An  auth_sessionobject is normally created for every client instance. | 
| auth_session [Http_client] | 
An  auth_sessionrepresents an authenticated session | 
| C | |
| cgi [Netcgi_fcgi] | 
The usual  Netcgi.cgiclass with FCGI specific methods. | 
| cgi [Netcgi] | 
Object symbolizing a CGI-like request/response cycle.
 | 
| cgi_activation [Netcgi1_compat.Netcgi_types] | 
Portage: In addition to defining a type, the following
       cgi_activationalso defines a conversion function that allows
      to connect old scripts to the new infrastructure. | 
| cgi_activation [Netcgi] | 
Alternate, more descriptive name for  cgi | 
| cgi_argument [Netcgi1_compat.Netcgi_types] | 
Portage: In addition to defining a type, the following
       cgi_argumentalso defines a conversion function that allows to
      connect old scripts to the new infrastructure. | 
| cgi_argument [Netcgi] | 
Represent a key-value pair of data passed to the script (including
    file uploads).
 | 
| cgi_argument [Netcgi_common] | 
See  Netcgi.cgi_argument. | 
| cgi_environment [Netcgi1_compat.Netcgi_env] | |
| cgi_environment [Netcgi] | 
The environment of a request consists of the information available
    besides the data sent by the user (as key-value pairs).
 | 
| client_socket_connector [Uq_engines] | 
This class type provides engines to connect to a service.
 | 
| compl_in_channel [Netchannels] | 
Further methods usually supported by ocamlnet channel implementations.
 | 
| compl_out_channel [Netchannels] | 
Further methods usually supported by ocamlnet channel implementations.
 | 
| config_file [Netplex_types] | |
| container [Netplex_types] | |
| controller [Netplex_types] | |
| controller_config [Netplex_types] | |
| D | |
| datagram_multiplex_controller [Uq_engines] | 
Additional methods for unconnected datagram handling
 | 
| datagram_socket_provider [Uq_engines] | 
This is a factory for  wrapped_datagram_socketobjects. | 
| dynamic_workload_config [Netplex_workload] | |
| E | |
| engine [Uq_engines] | 
This class type defines the interface an engine must support.
 | 
| enhanced_raw_in_channel [Netchannels] | 
Defines private methods reading text line by line
 | 
| event_system [Unixqueue] | 
The  event_systemmanages events, handlers, resources, groups,
 etc. | 
| extended_async_environment [Nethttpd_engine] | |
| extended_environment [Nethttpd_types] | 
Same as  v_extended_environment, but no virtual methods | 
| F | |
| ftp_data_engine [Ftp_data_endpoint] | 
The common type of FTP data engines
 | 
| ftp_method [Ftp_client] | 
An  ftp_methodis a small procedure doing some task | 
| H | |
| http_call [Http_client] | 
The container for HTTP calls
 | 
| http_engine_config [Nethttpd_engine] | |
| http_engine_processing_config [Nethttpd_engine] | |
| http_engine_processing_context [Nethttpd_engine] | |
| http_header [Nethttp] | |
| http_header_ro [Nethttp] | 
The HTTP header is represented as MIME header
 | 
| http_processor_config [Nethttpd_reactor] | |
| http_protocol_config [Nethttpd_kernel] | 
Configuration values for the HTTP kernel
 | 
| http_reactive_request [Nethttpd_reactor] | |
| http_reactor_config [Nethttpd_reactor] | |
| http_request_header_notification [Nethttpd_engine] | |
| http_request_notification [Nethttpd_engine] | |
| http_response [Nethttpd_kernel] | 
Encapsultation of the HTTP response for a single request
 | 
| http_service [Nethttpd_types] | |
| http_service_generator [Nethttpd_types] | |
| http_service_receiver [Nethttpd_types] | |
| http_trailer [Nethttp] | |
| http_trailer_ro [Nethttp] | 
The HTTP trailer is represented as MIME header
 | 
| I | |
| in_obj_channel [Netchannels] | 
The application-level input channel supports raw and complemented methods
 | 
| in_obj_stream [Netstream] | 
An  in_obj_streamextendsin_obj_channelby look-ahead methods | 
| in_record_channel [Ftp_data_endpoint] | 
An  in_record_channelcan be used to read files with record
 structure. | 
| internal_environment [Nethttpd_reactor] | 
For private use only
 | 
| io_obj_channel [Netchannels] | 
A channel supporting both input and output.
 | 
| J | |
| job_handler_engine_type [Shell_uq] | 
In addition to the  system_handler_engine_type, this type of engine
 returns thejoband thejob_instance. | 
| K | |
| key [Http_client] | 
A  keyis a user/password combination for a certain realm | 
| key_handler [Http_client] | |
| L | |
| logger [Netplex_types] | |
| logger_factory [Netplex_types] | |
| M | |
| mime_body [Netmime] | 
A MIME body with both read and write method.
 | 
| mime_body_ro [Netmime] | 
This is the read-only version of a MIME body.
 | 
| mime_header [Netmime] | 
A MIME header with both read and write method.
 | 
| mime_header_ro [Netmime] | 
This is the read-only version of a MIME header.
 | 
| min_config [Nethttpd_types] | 
Minimal configuration needed for  output_std_response | 
| multi_file_config [Netplex_log] | |
| multiplex_controller [Uq_engines] | 
A  multiplex_controlleris a quite low-level device to abstract
 bidirectional socket connections. | 
| N | |
| netplex_config [Netplex_types] | |
| O | |
| out_obj_channel [Netchannels] | 
The application-level output channel supports raw and complemented methods
 | 
| out_record_channel [Ftp_data_endpoint] | 
An  out_record_channelcan be used to output files with record
 structure. | 
| P | |
| par_thread [Netplex_types] | |
| parallelizer [Netplex_types] | |
| processor [Netplex_types] | |
| processor_factory [Netplex_types] | |
| processor_hooks [Netplex_types] | |
| protocol [Netplex_types] | |
| R | |
| raw_in_channel [Netchannels] | 
Basic Unix-level class type for input channels as used by ocamlnet.
 | 
| raw_io_channel [Netchannels] | 
A channel supporting both input and output.
 | 
| raw_out_channel [Netchannels] | 
Basic Unix-level class type for output channels as used by ocamlnet.
 | 
| rec_in_channel [Netchannels] | 
Recommended input class type for library interoperability.
 | 
| rec_out_channel [Netchannels] | 
Recommended output class type for library interoperability.
 | 
| rpc_multiplex_controller [Rpc_transport] | |
| rw_cgi_argument [Netcgi] | 
Old deprecated writable argument type.
 | 
| rw_cgi_argument [Netcgi_common] | |
| S | |
| server_socket_acceptor [Uq_engines] | 
This class type is for service providers that listen for connections.
 | 
| server_socket_listener [Uq_engines] | 
This class type represents factories for service providers
 | 
| simple_message [Netcgi1_compat.Netcgi_types] | |
| socket_config [Rpc_server] | |
| socket_config [Rpc_client] | 
Configuration for  `Socket(see below). | 
| socket_controller [Netplex_types] | |
| socket_service [Netplex_types] | |
| socket_service_config [Netplex_types] | |
| ssl_multiplex_controller [Uq_ssl] | 
The  ssl_multiplex_controlleris an extended multiplex controller
 which can also control SSL handshakes. | 
| system_handler_engine_type [Shell_uq] | 
This engine type can be passed as  system_handlertoShell_sys.register_jobin order to watch a running job. | 
| T | |
| trans_out_obj_channel [Netchannels] | 
A transactional output channel has a buffer for uncommitted data.
 | 
| V | |
| v_extended_environment [Nethttpd_types] | 
An extension of  cgi_environmentfor use with the daemon. | 
| v_processor [Netplex_kit] | 
Same as  processor, but the methodsprocessandsupported_ptypesare flagged asvirtual | 
| W | |
| workload_manager [Netplex_types] | |
| workload_manager_factory [Netplex_types] | |
| wrapped_datagram_socket [Uq_engines] | 
A  wrapped_datagram_socketallows datagrams to be sent via proxies. | 
