CppCMS Blog :: FastCGI

What's Next?

The road map of the project includes two important milestones:

CppCMS core components refactoring including following:
- Removal of dependency on CgiCC – today there is about 5% of CgiCC library is used, many features are not supported by it or are not supported well. For example: file upload handling in CgiCC is very primitive, limited and error prone, support of cookies buggy and so on.
- Using of Boost.Asio as internal event handler, because:
  1. It provides transparent synchronous and asynchronous event handling allowing future implementation of server push technologies.
  2. It provides efficient timer based event handling.
- Removal dependency of libfcgi and writing Boost.Asio friendly implementation of FastCGI/SCGI connectors. Implementation of HTTP connectors as well.
- Support of plug-in applications in CppCMS framework.
- Improving compilation speed by representing more pimpl idioms and removal of unnecessary classes.
Better support of i18n and and l10n:
- Transparent support of std::wstring with forms including automatic encoding testing and conversion.
- Support of std::locale for localization for outputs like numbers, dates, monetary, translation and so on.
- Optional support of ICU and icu::UnicodeString and icu::Locale that would add unsupported features by std::locale and allow replacement std::locale features with more correct implementations provided by ICU.

These changes will significantly break API backward compatibility, but it would be possible to adopt the code almost "mechanically" to the new API.

more...

API Changes and mod-prefork

There have been lot of work in recent weeks in order to make deep internal changes in the framework. Now they include:

Transparent support of 3 web server APIs: fastcgi, cgi and scgi.
Support of new mod prefork that allows safer management of worker processes.
Implementation of a cache that is shared between forked processes.

more...

Components of CppCMS

There are several important components that CppCMS implements:

FastCGI Application Framework
Easy Berkeley DB – Simple API to BDB
Templates System
Text Tools – text to html conversion tools
Nice URLs support

I'll describe there all these in details there

more...

Benchmarks, First Results

Updated 28/12/07, 17:00

In order to show that all the time I had spend on this system wasn’t wasted I had run a simple benchmark tests on following setup:

Server

Hardware: AMD Athlon XP 3000+ 64 bit, 1GB RAM.
OS: Debian Etch 64 bit.
Web server: Lighttpd 1.4.13
CMS: This blog software, configured with 5 working threads.
Data base of 85MB: 5,000 articles with 10 comments to each one.

Network devices

100Mbit network cards
Edimax $75 home router

Client

Hardware: Dell Latitude C400, PIII 750MHz, 256MB RAM
OS: Debian Etch 32 bit

more...

The Goals

When I started working on this project, many were (and still are) extremely skeptical about its future. Many questions were asked, like: "Are you masochist? Who you think will ever use it? The hardware is cheap, we do not need such things!" etc.

In this post I'll explain my point of view and I'll show why "C++ Web Development Framework" is more then just "yet another crazy idea of another geek"

more...