On 8/27/16 1:19 PM, Christian Grothoff wrote: > Dear all, > > > I'm happy to announce the release of libmicrohttpd 0.9.47. > > GNU libmicrohttpd is a small C library that is supposed to make it easy > to run an HTTP server as part of another application. GNU libmicrohttpd > is fully HTTP 1.1 compliant and supports IPv6. Finally, GNU > libmicrohttpd is fast, portable and has a simple API and (without TLS > support and other optional features) a small binary size (~32k). > > > This is a maintenance release. Changes include: > * fixed possible crash on malformed request > * fixes related to handling operating at configured connection limit > * internal refactoring for nicer platform abstractions > * improved error reporting > * unit tests for mhd_str.c functions > * add support for 308 status code >
I'm confused by this new configure option --disable-thread-names. I get what it does from the description, but why would you expose such an option to the user? What advantage/disadvantage are there to naming MHD threads? -- Anthony G. Basile, Ph. D. Chair of Information Technology D'Youville College Buffalo, NY 14201 (716) 829-8197
