Hi mongoose-users,
This is an announcement of 5.0 release.

In this release:
  o  Internal core has been changed from blocking, thread-per-connection to
      non-blocking, asynchronous, one thread for all.
  o  API modification for server creation and response creation. That
allowed
     keep-alive support for dynamic requests, boosting the embedded
performance
     to 100+ thousands requests per second on a single core
     (as measured on my development MacBook laptop)
  o Unified handling of POST requests and Websocket requests by putting a
payload
     into conn->content, conn->content_len attributes. That simplified user
code and
     eliminated the need of mg_read(), since mongoose buffers all data
prior to
     calling the callback
  o keep-alive support is the default
  o Dropped SSI support and throttling support
  o  Several configuraition parameters are gone:
       cgi_environment (replaced with MONGOOSE_CGI),
       protect_uri (not useful)
       ssi_pattern (SSI support is gone)
       throttle (throttling support is gone)
       error_log_file (not used)
       enable_keep_alive (enabled by default)
       listening_ports (renamed to listening_port)
       num_threads (core has changed to single thread)
       put_delete_auth_file (renamed to dav_auth_file)
       authentication_domain (renamed to auth_domain)
   o Due to the async, non-blocking nature of the core, few restrictions
are now
      in place:
           - user callbacks must not block
           - POST and Websocket data are now buffered, and cannot be huge
    o mongoose is now capable on listening on only one port

Updated documentation is at http://cesanta.com/#docs

Happy New Year,
Sergey.

-- 
You received this message because you are subscribed to the Google Groups 
"mongoose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mongoose-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to