---
name: "Eliom_react.Down.server"
section: "3o"
platform: "linux"
package: "libeliom-ocaml-doc"
version: "4.0.0-2"
release: "Debian 8 (Jessie)"
platforms: ["linux"]
url: "https://new.carta.tech/Eliom_react.Down.server"
---

# Eliom\_react.Down.server(3o)

Event from server to client.

## NAME

Eliom\_react.Down - Event from server to client.

## Module

Module   Eliom\_react.Down

## Documentation

Module **Down**\
  :  **sig end**

Event from server to client.

**=== A Down event (AKA down-going event) is an event which occurrences are** **transmitted asynchronously to the client. Even if they are named events ,** **it might be better to consider them as asynchronous server-to-client** **edges in the react events dependency graph.** **To use this, call function of\_react on server side,** **and just use the returned value as a react event on client side.** **Example:** **let e = of\_react ... in ... {{ ... React.E.map f %e; ... }} ===**

*type* **'a** *t*

The abstract type of down events.

*val of\_react* :  **?scope:\[\< Eliom\_comet.Channel.comet\_scope \] -\>** **?throttling:float -\>** **?name:string -\> ?size:int -\> 'a React.E.t -\> 'a t**

**of\_react ?scope ?throttling ?name e** create an asynchronous edge originating from  **e** . The parameters are:

\- **throttling** for the limit to event propagation rate (minimum time, in second, between two consecutive events - other events are lost),

\- **name** for named edges,

\- **size** for the size of the server side buffer.

\- **scope** tell which kind of channel this rely on (See  **Eliom\_comet.create** ).