be9fb919d1
1) This makes lwsws run a parent process with the original permissions. But this process is only able to respond to SIGHUP, it doesn't do anything else. 2) You can send this parent process a SIGHUP now to cause it to - close listening sockets in existing lwsws processes - mark those processes as to exit when the number of active connections on the falls to zero - spawn a fresh child process from scratch, using latest configuration file content, latest plugins, etc. It can now reopen listening sockets if it chooses to, or open different listen ports or whatever. Notes: 1) lws_context_destroy() has been split into two pieces... the reason for the split is the first part closes the per-vhost protocols, but since they may have created libuv objects in the per-vhost protocol storage, these cannot be freed until after the loop has been run. That's the purpose of the second part of the context destruction, lws_context_destroy2(). For compatibility, if you are not using libuv, the first part calls the second part. However if you are using libuv, you must now call the second part from your own main.c after the first part.
16 lines
609 B
Markdown
16 lines
609 B
Markdown
##Libwebsockets API introduction
|
|
|
|
Libwebsockets covers a lot of interesting features for people making embedded servers or clients
|
|
|
|
- http(s) serving and client operation
|
|
- ws(s) serving and client operation
|
|
- http(s) apis for file transfer and upload
|
|
- http POST form handling (including multipart)
|
|
- cookie-based sessions
|
|
- account management (including registration, email verification, lost pw etc)
|
|
- strong ssl PFS support (A+ on SSLlabs test)
|
|
|
|
You can browse by api category <a href="modules.html">here</a>
|
|
|
|
A collection of READMEs for build, coding, lwsws etc are <a href="pages.html">here</a>
|
|
|