Pipe_rpc_exn (p.babel.v0.16.0.doc.babel.Babel.Caller.Pipe_rpc

type ('q, 'r) dispatch :=
  'q ->
  ('r Async_kernel.Pipe.Reader.t * Async_rpc_kernel.Rpc.Pipe_rpc.Metadata.t)
    Async_kernel.Deferred.t

Source

val dispatch_multi : 
  ?metadata:Async_rpc_kernel.Rpc_metadata.t ->
  ('q, 'r) dispatch t ->
  Async_rpc_kernel.Versioned_rpc.Connection_with_menu.t ->
  ('q, 'r) dispatch

Determine which supported dispatch strategy to use and invoke the chosen rpcs. To unsubscribe, you can close the pipe.

Source

val singleton : 
  ('q, 'r, _) Async_rpc_kernel.Rpc.Pipe_rpc.t ->
  ('q, 'r) dispatch t

Create a new caller supporting a single rpc.

Source

val add : 
  ('q, 'r) dispatch t ->
  rpc:('q, 'r, 'e) Async_rpc_kernel.Rpc.Pipe_rpc.t ->
  ('q, 'r) dispatch t

Add support for dispatching another rpc. dispatch_multi will prefer this rpc over the ones the caller already supports.

Sourceval map_query : ('q1, 'r) dispatch t -> f:('q2 -> 'q1) -> ('q2, 'r) dispatch t

A specialization of map for the query type of a protocol.

Source

val map_response : 
  ('q, 'r1) dispatch t ->
  f:('r1 -> 'r2) ->
  ('q, 'r2) dispatch t

A specialization of map for the response type of a protocol.

Sometimes, Caller.Pipe_rpc_exn.map_response is not sufficient. For example, sometimes it might not be possible to convert the response to the desired type, in which case it may be appropriate to drop the value from the pipe entirely. For such cases, use Caller.map_response instead. It gives you access to the pipe itself, not just the values inside it, allowing you to use something like Pipe.filter_map.

Source

val filter_map_response : 
  ('q, 'r1) dispatch t ->
  f:('r1 -> 'r2 option) ->
  ('q, 'r2) dispatch t

Same as map_response but filters out some responses from the response pipe