package rpc_parallel

You can search for identifiers within the package.

in-package search v0.2.0

Type-safe parallel library built on top of Async_rpc

Install

Dune Dependency

github.com Changelog MIT License Edit opam file Versions (6)

Authors

J

Jane Street Group, LLC

Maintainers

J

Jane Street developers

Sources

rpc_parallel-v0.16.0.tar.gz

sha256=1e6e85e9f7cf3c1c221ceaa8c0d7a2370d402ae2ee12d68aefb6ebe47ef33016

doc/rpc_parallel.krb/Rpc_parallel_krb_public/Mode/index.html

Module `Rpc_parallel_krb_public.Mode`Source

Sourcemodule Kerberized : sig ... end

Sourcetype t =

| Kerberized of Kerberized.t
| For_unit_test

include Core.Bin_prot.Binable.S with type t := t

include Bin_prot.Binable.S_only_functions with type t := t

Sourceval bin_size_t : t Bin_prot.Size.sizer

Sourceval bin_write_t : t Bin_prot.Write.writer

Sourceval bin_read_t : t Bin_prot.Read.reader

Sourceval __bin_read_t__ : (int -> t) Bin_prot.Read.reader

This function only needs implementation if t exposed to be a polymorphic variant. Despite what the type reads, this does *not* produce a function after reading; instead it takes the constructor tag (int) before reading and reads the rest of the variant t afterwards.

Sourceval bin_shape_t : Bin_prot.Shape.t

Sourceval bin_writer_t : t Bin_prot.Type_class.writer

Sourceval bin_reader_t : t Bin_prot.Type_class.reader

Sourceval bin_t : t Bin_prot.Type_class.t

include Sexplib0.Sexpable.S with type t := t

Sourceval t_of_sexp : Sexplib0.Sexp.t -> t

Sourceval sexp_of_t : t -> Sexplib0.Sexp.t

Source

val kerberized : 
  key_source:Krb_public.Server_key_source.t ->
  conn_type:Krb_public.Conn_type.t ->
  unit ->
  t

In this mode, communication to and from workers will use Kerberos for authentication.

key_source must be a valid key source for all the hosts where a worker is running. For example, if your key source specifies a keytab path, that path must have a valid keytab on hosts where you spawn a worker.

conn_type specifies the level of protection for the rpc communication to and from workers. If your application is extremely performance sensitive and sends a lot of data to and from your workers, you should use Auth. Otherwise, using Priv as a default is appropriate. See lib/krb/public/src/conn_type.mli for more documentation.

Regardless of what conn_type you choose, connections will only be accepted from principals that match the principal associated with key_source. By default, this is the principal associated with the user that started the rpc_parallel process.

Sourceval for_unit_test : t

In this mode, communication to and from workers will not be kerberized. This is only appropriate if you are running a test.