From 3abc97219062604f3b4efb0ba8cb3ab135d3374b Mon Sep 17 00:00:00 2001 From: Andy Green Date: Tue, 3 Dec 2019 10:47:05 +0000 Subject: [PATCH] sul: export sul-specific internal apis for special cases Normally these apis are wrapped by the other public exports, but in the case your code wants to use lws_sul standalone and may or may not be linked to lws itself, the internal api level is more suited. --- include/libwebsockets/lws-timeout-timer.h | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/include/libwebsockets/lws-timeout-timer.h b/include/libwebsockets/lws-timeout-timer.h index 9a0f2959f..75f59ddb6 100644 --- a/include/libwebsockets/lws-timeout-timer.h +++ b/include/libwebsockets/lws-timeout-timer.h @@ -251,4 +251,16 @@ lws_sul_schedule(struct lws_context *context, int tsi, LWS_VISIBLE LWS_EXTERN void lws_validity_confirmed(struct lws *wsi); +/* + * These are not normally needed, they're exported for the case there's code + * using lws_sul for which lws is an optional link dependency. + */ + +LWS_VISIBLE LWS_EXTERN int +__lws_sul_insert(lws_dll2_owner_t *own, lws_sorted_usec_list_t *sul, + lws_usec_t us); + +LWS_VISIBLE LWS_EXTERN lws_usec_t +__lws_sul_service_ripe(lws_dll2_owner_t *own, lws_usec_t usnow); + ///@}