mirror of
https://libwebsockets.org/repo/libwebsockets
synced 2025-05-03 15:39:53 +00:00
Compare commits
3 commits
Author | SHA1 | Date | |
---|---|---|---|
![]() |
ab9df9cfc3 | ||
![]() |
2ce0be3284 | ||
![]() |
6414a1b63c |
3 changed files with 3 additions and 3 deletions
|
@ -410,7 +410,7 @@ set(CPACK_RPM_PACKAGE_LICENSE "MIT")
|
|||
set(CPACK_PACKAGE_NAME "${PACKAGE}")
|
||||
set(CPACK_PACKAGE_VERSION_MAJOR "4")
|
||||
set(CPACK_PACKAGE_VERSION_MINOR "3")
|
||||
set(CPACK_PACKAGE_VERSION_PATCH_NUMBER "3")
|
||||
set(CPACK_PACKAGE_VERSION_PATCH_NUMBER "5")
|
||||
|
||||
set(CPACK_PACKAGE_VERSION_PATCH "${CPACK_PACKAGE_VERSION_PATCH_NUMBER}-${LWS_BUILD_HASH}")
|
||||
set(CPACK_PACKAGE_RELEASE 1)
|
||||
|
|
|
@ -190,7 +190,7 @@ a UDP socket pair that the event loop waits on. When the wake is handled by the
|
|||
lws event loop thread, it will broadcast a `LWS_CALLBACK_EVENT_WAIT_CANCELLED`
|
||||
message to every vhost-protocol instantiation, so you can handle this callback,
|
||||
usually lock a shared data region, and if you see you need to write, call
|
||||
`lws_callback_on_writeable()` for the wsi(s) that need to write.
|
||||
`lws_callback_on_writable()` for the wsi(s) that need to write.
|
||||
|
||||
There's no restriction on multiple threads calling `lws_cancel_service()`, it's
|
||||
unconditionally safe due to how it is implemented underneath.
|
||||
|
|
|
@ -154,7 +154,7 @@ lws_adns_iterate(lws_adns_q_t *q, const uint8_t *pkt, int len,
|
|||
const char *expname, lws_async_dns_find_t cb, void *opaque)
|
||||
{
|
||||
const uint8_t *e = pkt + len, *p, *pay;
|
||||
struct label_stack stack[4];
|
||||
struct label_stack stack[8];
|
||||
int n = 0, stp = 0, ansc, m;
|
||||
uint16_t rrtype, rrpaylen;
|
||||
char *sp, inq;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue