---
name: "Eliom_react.Up.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.Up.server"
---

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

Event from client to server.

## NAME

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

## Module

Module   Eliom\_react.Up

## Documentation

Module **Up**\
  :  **sig end**

Event from client to server.

**=== Up events are quite different from Down events. Because of the** **asymmetrical nature of web programming and because of the reactive model** **used, an Up event must be created on the server and wrapped into a** **callback (or something the client can build a callback with).** **Example of use:** **let e\_up = Eliom\_react.Up.create** **(Eliom\_parameter.ocaml a Json.t\<string\>)** **in** **... {{ ignore ( %e\_up A ) }} ...** **===**

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

The type of events that, while being "on the server", are triggered by clients. On the server such an event is /primitive/ (hence the  **create** function) whereas it is /effect-full/ on the client.

*val to\_react* :  **'a t -\> 'a React.E.t**

**to\_react e** injects the up events  **e** into react events so that it can be manipulated as a standard event.

*val create* :  **?scope:Eliom\_common.scope -\>** **?name:string -\>** **('a, \[ \`WithoutSuffix \],** **\[ \`One of 'a Eliom\_parameter.ocaml \] Eliom\_parameter.param\_name)** **Eliom\_parameter.params\_type -\> 'a t**

**create param** creates an Up event. If  **~name** is present, the coservice used to transmit the event will always have the same name, even if the server is restarted. **~scope** describes the visibility of the event. By default, it is **\`Site** if it is called during initialisation, **\`Client\_process** otherwise.