Andy Green a57d13cb1b smp: adopt: deal with load balancing init window ... With SMP as soon as we add the new sockfd to the fds table, in the case we load-balanced the fd on to a different pt, service on it becomes live immediately and concurrently. This can lead to the unexpected situation that while we think we're still initing the new wsi from our thread, it can have lived out its whole life concurrently from another service thread. Add a volatile flag to inform the owning pt that if it wants to service the wsi during this init window, it must wait and retry next time around the event loop.		2019-03-10 08:02:02 +08:00
..
adopt.c	smp: adopt: deal with load balancing init window	2019-03-10 08:02:02 +08:00
client.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
close.c	cgi: fix stdin cgiwsi leak when closed early	2019-03-10 08:02:02 +08:00
connect.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
dummy-callback.c	cgi: fix stdin cgiwsi leak when closed early	2019-03-10 08:02:02 +08:00
network.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
output.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
pollfd.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
private.h	smp: adopt: deal with load balancing init window	2019-03-10 08:02:02 +08:00
server.c	server-status: add proc statm and switch to vhost protocol timer	2019-03-10 08:02:02 +08:00
service.c	smp: adopt: deal with load balancing init window	2019-03-10 08:02:02 +08:00
stats.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
vhost.c	LWS_WITH_NETWORK: cmake option for no network code	2019-01-13 07:54:57 +08:00
wsi-timeout.c	lws_http_mark_sse	2019-01-30 20:59:56 +08:00
wsi.c	lws_http_mark_sse	2019-01-30 20:59:56 +08:00