"C Server Pages" is a C++ application server. It runs server pages written in HTML with C++ embedded and templates with C++ beans. It features scalability and integration with the backend, multiprocess and multithread functionality, and it is tunable, load balancing, and behaves well even when highly loaded.
Calendars for the Web provides a server based calendar and scheduling application. It allows unlimited users to share unlimted events per calendar. Calendars for the Web comes with a full-featured browser based interface, is completely customizable (sixteen different calendar view types), fully documented, and supports online administration.
CGI_UTILS is a set of three C++ classes: CGI, Template, and Session. CGI wraps the CGI protocol. Template provides an easy way to use templates in your CGI applications. It knows about variables and datasets (tables). Session provides the ability to pass data between your programs through shared memory.
MaxiWeb is a toolkit that helps you build standalone self-launching Web server applications. The toolkit includes example programs, a C++ class library, an Active Server Page compiler, and various command line tools. Programs built with the MaxiWeb toolkit can take the place of larger Web servers such as Netscape Server, Apache, and Microsoft IIS. Using the Active Server Page (C++ ASP) compiler and 5 lines of C++ code, you can Web enable your new or existing application in just minutes. Complete MaxiWeb enabled applications can be as small as 60K.
Sablotron is an XML toolkit which implements XSLT, DOM, and XPath. Sablotron is written in C++, and it can be used from C, Perl, Python, PHP, ObjectPascal, and via a command line interface. It supports the XSLT 1.0, XPath 1.0, and DOM Level 2 W3C specifications. It is designed to be as compact and portable as possible, and is maintained as an Open Source project by Ginger Alliance.
The SOAP to CORBA bridge/translator is written entirely in C++ and shows that it is indeed possible to do a generic translation of SOAP requests to CORBA method invocations and vice versa. This is implemented by using the CORBA Interface repository to match the incoming SOAP request to the corresponding CORBA service, build the dynamic invocation of the CORBA service, and generate the SOAP response (or possibly SOAP fault in the case of a CORBA user exception, for instance).