|
3 | 3 |
|
4 | 4 | Minimal HTTP server using good old threads, with stream abstractions, |
5 | 5 | simple routing, URL encoding/decoding, and optional compression with camlzip. |
| 6 | +It also supports [server-sent events](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events) |
| 7 | +([w3c](https://html.spec.whatwg.org/multipage/server-sent-events.html#event-stream-interpretation)) |
6 | 8 |
|
7 | | -Free from all forms of `ppx`, async monads, etc. |
| 9 | +Free from all forms of `ppx`, async monads, etc. 🙃 |
8 | 10 |
|
9 | 11 | **Note**: it can be useful to add the `jemalloc` opam package for long running |
10 | 12 | server, as it does a good job at controlling memory usage. |
@@ -75,11 +77,11 @@ dependencies or high scalability libraries. |
75 | 77 |
|
76 | 78 | Use cases might include: |
77 | 79 |
|
78 | | -- serve content directly from a static blog generator |
79 | | -- provide a web UI to some tool (like CUPS and syncthing do) |
80 | | -- implement a basic monitoring page for a service |
81 | | -- provide a simple json API for a service, on top of http |
82 | | -- use `http_of_dir` to serve odoc-generated docs or some assets directory |
| 80 | +- serve content directly from a static blog generator; |
| 81 | +- provide a web UI to some tool (like CUPS and syncthing do); |
| 82 | +- implement a basic monitoring page for a service; |
| 83 | +- provide a simple json API for a service, on top of http; |
| 84 | +- use `http_of_dir` to serve odoc-generated docs or some assets directory. |
83 | 85 |
|
84 | 86 | ## Documentation |
85 | 87 |
|
|
0 commit comments