mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-23 00:00:06 +01:00
d8ccfc2370
In the case code is composed into a single process, but it isn't monolithic in the sense it's made up of modular "applications" that are written separate projects, provide a way for the "applications" to request a callback from the lws event loop thread context safely. From the callback the applications can set up their operations on the lws event loop and drop their own thread. Since it requires system-specific locking to be threadsafe, provide a non-threadsafe helper and then indirect the actual usage through a user-defined lws_system ops function pointer that wraps the unsafe api with the system locking to make it safe. |
||
|---|---|---|
| .. | ||
| adopt.c | ||
| client.c | ||
| close.c | ||
| connect.c | ||
| detailed-latency.c | ||
| dummy-callback.c | ||
| lws-dsh.c | ||
| network.c | ||
| output.c | ||
| pollfd.c | ||
| private-lib-core-net.h | ||
| sequencer.c | ||
| server.c | ||
| service.c | ||
| sorted-usec-list.c | ||
| state.c | ||
| stats.c | ||
| vhost.c | ||
| wsi-timeout.c | ||
| wsi.c | ||