aboutsummaryrefslogtreecommitdiff
path: root/README.build
diff options
context:
space:
mode:
authorAndy Green <andy.green@linaro.org>2013-02-18 10:22:42 +0800
committerAndy Green <andy.green@linaro.org>2013-02-18 10:22:42 +0800
commitcc7cb68ded898cf225ffb390273791d34d685dd4 (patch)
treee12bb994dbdc35d2a2348ade4680f3017db95d41 /README.build
parent0caf9c5acb00083ee21a70bd219079289c0ff02f (diff)
downloadlibwebsockets-cc7cb68ded898cf225ffb390273791d34d685dd4.tar.gz
remove header name buffer
The header name buffer and its max length handling has actually been unused since the minilex parser was introduced. We hold parsing state in the lex-type parts and don't need to store or worry about max length, since the parser will let us know as soon as it can't be a match for the valid header names. This strips it out reducing the per-connection allocation for x86_64 with default configure from 224 to 160. Signed-off-by: Andy Green <andy.green@linaro.org>
Diffstat (limited to 'README.build')
-rw-r--r--README.build4
1 files changed, 0 insertions, 4 deletions
diff --git a/README.build b/README.build
index 4d23191f..62de012f 100644
--- a/README.build
+++ b/README.build
@@ -147,10 +147,6 @@ They all have reasonable defaults usable for all use-cases except resource-
constrained, so you only need to take care about them if you want to tune them
to the amount of memory available.
- - LWS_MAX_HEADER_NAME_LENGTH default 64: max characters in an HTTP header
-name that libwebsockets can cope with, if a header arrives bigger than this
-it's ignored until the next header is seen
-
- LWS_MAX_HEADER_LEN default 1024: allocated area to copy http headers that
libwebsockets knows about into. You only need to think about increasing this
if your application might have monster length URLs for example, or some other