Andy Green d8ccfc2370 lws_system: helpers for attaching to existing event loop from other threads ... 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.		2020-01-05 22:17:58 +00:00
..
alloc.c	freertos: rename esp32 plat to freertos	2019-08-26 09:58:57 +01:00
buflist.c	buflist: overallocate by 1	2019-10-13 07:17:03 +01:00
context.c	lws_system: helpers for attaching to existing event loop from other threads	2020-01-05 22:17:58 +00:00
libwebsockets.c	lws_strexp: flexible string expansion helper	2019-12-16 18:16:01 +00:00
logs.c	logs: use single nonmonotonic usec count	2020-01-02 08:30:54 +00:00
lws_dll.c	private.h: rename to contain dir	2019-08-15 10:49:52 +01:00
lws_dll2.c	format strings: fixes for when toolchain has uint32_t as unsigned long	2019-11-05 21:00:45 +00:00
private-lib-core.h	lws_system: helpers for attaching to existing event loop from other threads	2020-01-05 22:17:58 +00:00
vfs.c	private.h: rename to contain dir	2019-08-15 10:49:52 +01:00