/usr/lib/ocaml/netplex/rpc_netplex.mli is in libocamlnet-ocaml-dev 4.0.4-1build3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 93 94 | (* $Id: rpc_netplex.mli 1557 2011-03-04 14:43:05Z gerd $ *)
(** Netplex support for RPC servers (TCP only) *)
open Netplex_types
val rpc_factory :
configure:(config_file -> address -> 'a) ->
?socket_config:('a -> Rpc_server.socket_config) ->
?hooks:('a -> processor_hooks) ->
?supported_ptypes:parallelization_type list ->
name:string ->
setup:(Rpc_server.t -> 'a -> unit) ->
unit ->
processor_factory
(** A factory for TCP-based RPC servers. In [name] the name of the processor
* is defined. This name can be referenced from the config file like:
*
* {[
* processor {
* type = "the passed [name]";
* ...
* }
* ]}
*
* Parameters may be included in the [processor] section:
* - [portmapper]: This is a boolean parameter. If set to true,
* the Internet port is registered with the portmapper program.
* This will fail if there are several Internet bindings with distinct
* port numbers!
* - [timeout]: This is a float parameter. It sets the transport
* timeout of the RPC server (see {!Rpc_server.set_timeout}).
* If a connection hangs for this number of seconds, it is
* shut down by the server.
*
* Further parameters and subsections can be defined by the user. These
* parameters should be parsed and checked for correctness by the
* [configure] callback. The result of [configure] is also passed
* to [setup] and other optional functions. The [configure] function is
* called just before the service is
* added to Netplex (i.e. from the controller context).
*
* The return value of [configure] can be of any type. This value
* exists once for every time the processor is instantiated (used) by a
* service. It is not only useful for passing configuration values
* down, but also for storing intermediate results while establishing
* the service.
*
* The [Rpc_server.t] structure is created every time a new connection
* is accepted. Of course, this is done from the context of the container.
* The [Rpc_server.t] is created without any binding; the user must
* bind procedures in the [setup] function. This can be done by calling
* [Rpc_server.bind] or the ocamlrpcgen-generated function (by the
* [-srv2] switch of ocamlrpcgen).
*
* For example, a minimal factory for an RPC service may look like:
*
* {[
* let proc_ping () = () (* Trivial RPC procedure *)
*
* let my_factory() =
* Rpc_netplex.rpc_factory
* ~name:"my_rpc_service"
* ~factory:(fun _ _ -> ())
* ~setup:(fun rpc () ->
* My_rpc_srv.bind ~proc_ping rpc
* )
* ()
* ]}
*
* The [setup] function is also called once before a new connection is
* accepted to get a list of programs and procedures. The [Rpc_server.t]
* is a special one in this case, and one can test for it with the
* {!Rpc_server.is_dummy} function.
*
* @param socket_config An optional function computing the socket
* configuration. By default, [Rpc_server.default_socket_config] is used.
* Special socket configuration would, for example, allow SSL.
*
* @param hooks An optional function returning the hooks to call.
* See [Netplex_types.processor_hooks] for documentation.
*
* @param supported_ptypes Which parallelization types are supported
* by the service. By default, both multi-processing and multi-threading
* are included in this list.
*)
val debug_rpc_internals : bool ref
val debug_rpc_service : bool ref
(** These variables control debugging of [Rpc_server]. If set, the
* debug messages are sent to the Netplex logger. These variables must
* be set before an RPC connection is accepted.
*)
|