From 4e2ac7685db31c294c079cebe2583775d6ea0be6 Mon Sep 17 00:00:00 2001 From: Andy Green Date: Sat, 26 Dec 2015 20:26:11 +0800 Subject: [PATCH] clarify changelog Signed-off-by: Andy Green --- changelog | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/changelog b/changelog index 134747c8..59604d01 100644 --- a/changelog +++ b/changelog @@ -110,12 +110,7 @@ allocated a buffer bigger than the library is going to use. The example apps no longer use LWS_SEND_BUFFER_POST_PADDING. -The only path who made use of it was sending with LWS_WRITE_CLOSE. - -If you use LWS_WRITE_CLOSE by hand in your user code, you need to allow an -extra 2 bytes space at the end of your buffer. This ONLY applies to -LWS_WRITE_CLOSE, which you normally don't send directly, but cause by returning -nonzero from a callback letting the library actually send it. +The only path who made use of it was sending with LWS_WRITE_CLOSE ---> 2) Because of lws_close_reason() formalizing handling close frames, LWS_WRITE_CLOSE is removed from libwebsockets.h. It was only of use to send