# Overview of the bindings
-The ***binder*** serves files through HTTP protocol and offers to
-developers the capability to offer application API methods through HTTP or
+The ***binder*** serves files through HTTP protocol and offers developers the capability to offer application API methods through HTTP or
WebSocket protocol.
The ***bindings*** are used to add **API** to ***binders***.
This part describes how to write a ***binding*** for ***binder***
or in other words how to add a new **API** to the system.
-Excepting this summary, this section target developers.
+This section target developers.
This section shortly explain how to write a binding
using the C programming language.
It is convenient to install the ***binder*** on the
desktop used for writing the binding.
-It allows easy debug and test.
+It allows for easy debug and test.
## Nature of a binding
It contains several **verbs** that implement the ***binding***
functionalities.
Each of these **verbs** is a **method** that
-processes requests of applications and sends result.
+processes requests of applications and sends results.
The ***binding***'s methods are invoked by HTTP or websocket
requests.
Running:
```bash
-afb-daemon --binding tuto-1.so --port 3333 --token ''
+afb-daemon --binding ./tuto-1.so --port 3333 --token ''
```
At this point, afb-daemon has started, it loaded the binding tuto-1.so and now
- The include to get for creating a binding
- How to declare the API offered by the binding
-- How to handle request made to the binding
+- How to handle requests made to the binding
### Getting declarations for the binding
Running:
```bash
-afb-daemon --binding tuto-2.so --port 3333 --token ''
+afb-daemon --binding ./tuto-2.so --port 3333 --token ''
```
Testing:
}
```
-In an other terminal:
+In another terminal:
```bash
$ afb-client-demo -H localhost:3333/api?token=toto