This is server API (go to client)

Module Eliom_pervasives

module Eliom_pervasives : sig..end

This module is automatically open by eliomc and js_of_eliom.


Client values

See the manual .

type 'a client_value = 'a Eliom_lib.client_value

Client values on the server are created by the syntax {typ{ expr }} in the server section (cf. the manual ). They are abstract, but become concrete once sent to the client. See also the concrete representation on the client .

RPC / Server functions

See the manual .

type ('a, 'b) server_function

A value of type ('a, 'b) server_function is created on the server from a function 'a -> 'b Lwt.t and provides a given function on the client side. See also the concrete client side representation .

val server_function : 
  ?scope:[< Eliom_common.scope ] ->
  ?options:unit ->
  ?charset:string ->
  ?code:int ->
  ?content_type:string ->
  ?headers:Http_headers.t ->
  ?secure_session:bool ->
  ?name:string ->
  ?csrf_safe:bool ->
  ?csrf_scope:[< Eliom_common.user_scope ] ->
  ?csrf_secure:bool ->
  ?max_use:int ->
  ?timeout:float ->
  ?https:bool ->
  ?error_handler:((string * exn) list -> 'b Lwt.t) ->
  'a Deriving_Json.t ->
  ('a -> 'b Lwt.t) -> ('a, 'b) server_function

server_function argument_type f creates a value of type Eliom_pervasives.​server_function . This allows to call f from the client. The first argument argument_type is an instance of Deriving_Json for the type of the argument. It is used to safely encode and decode the argument sent to the server.

The optional parameters correspond directly to the optional parameters of Eliom_registration.​Ocaml.​register_coservice' .

See also the manual .