CAPI app stopping

[gigagrig]

uWebSockets C++ library has way to safely stop server by scheduling socket closing with code like that.

loopToShutdown->defer([]() { us_listen_socket_close(...) });
The code can be invoked from any thread.

Does CAPI has a similar or another way to stop the app?

[cirospaciari]

@gigagrig

In my case i just use libuv to defer to me the close call, loop defer its not yet on C API.

You can get the native loop using:

    struct us_loop_t *uws_get_loop();
    struct us_loop_t *uws_get_loop_with_native(void* existing_native_loop);

uws_get_loop_with_nativebasically sets you the event loop and returns to you

    uv_loop_t *loop = (uv_loop_t *loop)uws_get_loop_with_native(uv_default_loop());

or

    uv_loop_t *loop =  ( uv_loop_t *)uws_get_loop();

and after this you can use any API of libuv like uv_prepare to close the API before pooling more IO, or uv_check to close the API after pooling more IO, if you want to call this from another thread (remembers that you can only have 1 App/SSLApp per thread) you can use async to wakeup the event loop in main thread and close to you

but libuv is not the only loop option, so i think is a good idea to add defer to CAPI in future

[gigagrig]

@cirospaciari thanks for detailed answer!
Now i'm starting to realize that using capi becomes more and more tricky.
So am a right that if i need to defer a reply, i also have to use API of libuv too? Because I cannot call uws_res_end and other reply functions in other than App/SSLApp thread?

[cirospaciari]

No you don't need to use libuv and you can't never use this library from other threads (it's not a thread safe library it's not the CAPI it's the design of uWS see the docs), you can use multiple threads (one app per thread) or signaling between threads, you don't need to use libuv, you can see examples on CAPI without libuv and using basically all resources.

[gigagrig]

I got it. I realized that I should use us_timer_set for async replies logic.
Thanks for help again!