package async_js

You can search for identifiers within the package.

in-package search v0.2.0

package async_js

async_js
- Async_js
  - Debug
  - Http
    
    Method_with_args
    
    Post_body
    
    Response
    
    Response_type
  - Persistent_connection
    
    Rpc
    
    Event
    
    Versioned_rpc
    
    Event
  - Rpc
    
    Connection
    
    Client_implementations
    
    Heartbeat_config
async_js.async_test
- Async_js_test
  - Expect_test_config
    
    IO
async_js.test_handle_garbage_collector
- Bonsai_test_handle_garbage_collector

Legend:
Library
Module
Module type
Parameter
Class
Class type

type t

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

val t_of_sexp : Sexplib0__.Sexp.t -> t

val sexp_of_t : t -> Sexplib0__.Sexp.t

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

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

val bin_size_t : t Bin_prot.Size.sizer

val bin_write_t : t Bin_prot.Write.writer

val bin_read_t : t Bin_prot.Read.reader

val __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.

val bin_shape_t : Bin_prot.Shape.t

val bin_writer_t : t Bin_prot.Type_class.writer

val bin_reader_t : t Bin_prot.Type_class.reader

val bin_t : t Bin_prot.Type_class.t

val create : 
  ?timeout:Core.Time_ns.Span.t ->
  ?send_every:Core.Time_ns.Span.t ->
  unit ->
  t

Each side of the connection has its own heartbeat config. It sends a heartbeat every send_every. If it doesn't receive any messages for timeout, whether it's a heartbeat or not, it drops the connection. It only checks whether timeout has elapsed when it sends heartbeats, so effectively timeout is rounded up to the nearest multiple of send_every.

val timeout : t -> Core.Time_ns.Span.t

val send_every : t -> Core.Time_ns.Span.t