Chart Gallery

http://code.google.com/p/gchart/

he main idea behind GChart is simple: You can make very nice charts efficiently out of a reasonably small number of 1-cell Grids (for the aligned labels) and (empty) Images (for everything else), styled and positioned appropriately on an AbsolutePanel. Not surprisingly, bar charts don't suffer at all under the limitations imposed by this strategy--but (as long as you don't mind using dotted connecting lines or banded-filled pie slices) line and pie charts also do remarkably well.

The new Symbol properties fillSpacing and fillThickness are central to GChart 2.0's new pie, line, and area chart capabilities. These let you control the spacing and size of the connecting dots in a line chart, and the spacing and thickness of the shading bands in a pie slice or area-filling curve. Since each additional dot or band adds an extra HTML element, these new properties make it easy to control your charts' visual-quality/performance tradeoff.

Ziproxy is forwarding, non-caching, compressing HTTP proxy server.

Ziproxy is forwarding, non-caching, compressing HTTP proxy server.
Basically it squeezes images by converting them to lower quality JPEGs or JPEG 2000 and compresses (gzip) HTML and other text-like data.
It also provides other features such as: HTML/JS/CSS optimization, preemptive hostname resolution, transparent proxying and more.

Ziproxy is an option when dealing with low-bandwidth cases like:

* ISPs providing dialup services
* ISPs providing mobile internet services
* HTTP WAN optimization cases
* Low bandwidth (or saturated) point-to-point connections in general

Ziproxy may be called a "web accelerator", although it is not the best name, considering the number of snake oil products advertised as such.

Ziproxy operates in daemon mode. It also may be invoked by (x)inetd if desired (not recommended for performance reasons).
It is HTTP/1.1-aware and compatible with HTTPS.

Currently it is known to be usable under the following OSes: Linux (Red Hat, Conectiva, Debian), FreeBSD and Cygwin (there were reports on Mac OS X and Solaris compatibility aswell).
It ran successfully under the following architectures: x86, x86-64 and SPARC32.
And it was successfully compiled under GNU GCC and Intel's ICC.

Ziproxy is available as a free (FOSS) software under the GNU GPL (version 2 or higher) license.
http://ziproxy.sourceforge.net/

AppWeb, the #1 Embedded WebServer Technology

AppWeb, the #1 Embedded WebServer Technology


Open Source Embedded Web ServersAppWeb™ is the leading web server technology for embedding in devices and applications. It is an open source, feature rich, embedded web server that has been designed from the ground up with security in mind. It is integrated directly into embedded systems and applications for simple and convenient deployment and with features such as server side Embedded JavaScript and Embedded Server Pages, AppWeb is in a league of its own when compared with other embedded web servers.

AppWeb is also highly efficient. It has a modular architecture that results in a very small memory footprint and minimal CPU requirements. Compared to other web servers, AppWeb consumes a fraction of the resources that other servers require. It also offers superior security and provides the easiest way to create dynamic, web based user and management interfaces.

SPAW Edito

http://spaweditor.com/en/disp.php/en_products/en_spaw/en_spaw_intro

SPAW Editor is a web based in-browser WYSIWYG editor control enabling web site developers to replace a standard textarea html control with full-featured, fully customizable, multilingual, skinable web based WYSIWYG editor. Version 2 adds tabbed multi-document interface, floating/shared toolbars, modular architecture and many other exciting features

Tntnet C++ Server Pages

C++ Dynamite for the Web
http://www.tntnet.org/

Tntnet is a modular, multithreaded, high performance webapplicationserver for C++. To create webapplications Tntnet has a template-language called ecpp similar to php, jsp or mason, where you can embed c++-code inside a html-page to generate active content. The ecpp-files are precompiled to c++-classes called components and compiled and linked into a shared library. This process is done at compiletime.

Because the webapplications are compiled into native code, they are very fast and compact. The webserver Tntnet needs only the compiled componentlibrary. Components can call other components. So you can create buildingblocks of html-parts and call them in other pages like subprocesses.

Requests are parsed by tntnet and the request-information is easily accessible to the components. It supports GET and POST-parameters and Mime-multipart-requests for file-upload. The templatelanguage has also support for internationalized applications. You can easily create webapplications for different languages.

Other features are: cookies, HTTP-upload, automatic request-parameter parsing and conversion, automatic sessionmanagement, scoped variables (application, request and session), internationalisation, keep-alive. Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of workerthreads, which answers requests from http-clients.

Ssl is supported via the gnutls- or openssl-library.