ULib - C++ library

Travis CI: Coverity Scan:

ULib is a highly optimized class framework for writing C++ applications. I wrote this framework as my tool for writing applications in various contexts. It is a result of many years of work as C++ programmer. I think, in my opinion, that its strongest points are simplicity, efficiency and sophisticate debugging.

ULib is meant as a very light-weight C++ library to facilitate using C++ design patterns even for very deeply embedded applications, such as for systems using uclibc along with posix threading support. For this reason, ULib disables language features that consume memory or introduce runtime overhead, such as rtti and exception handling, and assumes one will mostly be linking applications with other pure C based libraries rather than using the overhead of the standard C++ library and other similar class frameworks.

It include as application example a powerful search engine with relative web interface and a multi purpose server (plugin oriented) which results, out of John Fremlin accurate investigations, to be one of the fastest web application frameworks for serving small dynamic webpages (and also make easier the usage of shell scripts for CGI application)

userver (_tcp | _ssl | _ipc) application server (plugin oriented)

The current version offers the following features :

• HTTP/1.0 and 1.1 protocols supported and experimental implementations of HTTP/2 (h2spec compliant).
• Persistent connections for HTTP/1.1 and Keep-Alive support for HTTP/1.0.
• Browser cache management (headers: If-Modified-Since/Last-modified).
• Chunk-encoding transfers support.
• HTTP multi-range request support.
• Memory caching of document root for (small) static pages with smart gzip compression and CSS/JS reduction.
• Support for automatic update of caching document root with inotify (on Linux).
• Support for pipelining.
• Support for virtual hosts (also with SSL).
• Support for basic/digest authentication optionally based on url mask.
• Support for directory listings via basic/digest authentication.
• Support for uri protection.
• Support for aliases/redirection.
• Support for switch the site to a maintenance page only.
• Support for URL traffic based throttling (experimental).
• Support for overriden of error messages by local document (ErrorDocument/40x|500.html).
• Support for RewriteRule (lighttpd-like) that check for file existence as they do on Apache, some CMS (SilverStripe) require it.
• Support for (apache-like) log NCSA extended/combined format
• Support for JSONRequest.
• Accept HTTP uploads up to 4 GB without increasing memory usage.
• General CGI support (run any CGI script) with automatic output compression (using gzip method).
• CGI support for shell script processes (with automatic management of form and cookie).
• CGI support for the X-Sendfile feature and also supports X-Accel-Redirect headers transparently.
• Support for minify HTML CGI output by wrapping google page speed SDK.
• Support for running JavaScript code by wrapping google V8 JavaScript Engine.
• HTTP pseudo-streaming for FLV video managed transparently.
• C Servlet Support with libtcc (if available) as a backend for dynamic code generation (experimental).
• Support for running Ruby on Rails applications natively (experimental).
• Support for running natively PHP applications whith a php (embedded) library (experimental).
• Preforking mode to improve concurrency with dedicated process for long-time request.
• Support for Windows (without preforking).
• Customizable builds (you can remove unneeded functionality).
• Requests cut in phases for modular architecture (apache-like).
• Configuration file with dedicated section.
• Built-in modules :
  • mod_echo : echo features.
  • mod_rpc : generic Remote Procedure Call.
  • mod_http : core features, static file handler and dynamic page (ULib Servlet Page).
  • mod_ssi : Server Side Includes support with enhanced #set, direct include and #exec servlet (C/ULib Servlet Page).
  • mod_nocat : captive portal implementation.
  • mod_proxy : multi-features reverse proxy with websocket support.
  • mod_tsa : server side Time Stamp support.
  • mod_soap : generic SOAP server services support.
  • mod_fcgi : third-party applications support thru FastCGI interface.
  • mod_scgi : module that implements the client side of the SCGI protocol (experimental).
  • mod_shib : web single sign-on support (experimental).
  • mod_geoip : geolocation support (experimental).
  • mod_stream : simple streaming support (experimental).
  • mod_socket : Web Socket application framework (experimental).
• Security protection :
  • HTTP Session Hijacking mitigation.
  • Algorithmic Complexity Attacks prevention by randomizing hash seed.
  • DNS rebinding prevention by RFC1918 filtering and Host header validation.
  • selective uri support (DOS regex) for HTTP Strict Transport Security.
• Immune to Slow Read DoS attack
• High SSL server quality score

Who is Using ULib

It is the main software component of city of Florence wireless network

Benchmark

userver application server is since 10th round in the TechEmpower's web framework benchmarks. This independent work tests a large number of frameworks and platforms against a set of tests common to web applications, such as JSON serialization, database queries and templating.

Contributing

1. Fork it ( http://github.com//ULib/fork )
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

License

ULib is normally built and installed as a set of shared object libraries and header files. These libraries and headers are installed using directories selected through a "configure" script that has been prepared with automake and autoconf. As such, they should build and install similarly to and in a manner compatible and consistent with most other GNU software. ULib is Free Software under the LGPL and it is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Comments and suggestions are welcome.

stefano casazza <[email protected]>

Please, excuse me for my bad english, it's not my natural language, if some parts of this page seems wrong to you, feel free to suggest me better ones.