« Home | Web Platform Smack Down (Choosing a Server Side De... » | NetBank fails and goes under » | AnywhereCD closing September 30 » | GrandCentral - One Number fo Life » | HTTP GET, POST, and PUT with curl » | Agave Mountain, Inc. Privacy Policy » | Cleaning up a "new" PC » | Tax Issues for Nomadic Consultants » | Google Docs adds PowerPoint » | C++: Pragmatically Generating a Back Trace/Stack D... »

C++ Web Development Platform

After some serious consideration I've decided to go with an amalgimated approach to developing my web services architecture.  The pretty marketing stuff will be HTML/CSS/Flash, but the main applications will be written entirely in C++. 

Next, I resolved to leverage the Boost C++ Libraries and FastCGI.  FastCGI will remove the process creation from the invokation of a CGI application making the performance way faster. 

Lastly, I need to decide on the last piece or whether or roll my own. There is a limited number of C++ frameworks that are usable right "out of the box."  Some frameworks I am currently evaluating are:

  • Microsoft ATL Server.   The code is now located at: www.codeplex.com/atlserver.  License:  Microsoft Limited Permissive License (MS-LPL).
  • Leverage Apache/Axis & Apache mod.     
  • Microsoft IIS/IIS filters.
  • GNU Cgic.   GNU cgicc is an ANSI C++ compliant class library that greatly simplifies the creation of CGI applications for the World Wide Web.  This is basically a collection of classes and templates that hand you a parsed CGI environment.
  • WT.  Wt (pronounced wit-ty), is a C++ library to develop AJAX aware web applications, built around a graphical UI coneceptual framework.  This looks to be by far the coolest.  The question is will it stand up to some serious scrutany?
    •

    Requirements

    Given my previous embedded systems development I should be able to build up a system with a minimum linux install that is capable of saturating a 100MB ethernet connection. 

  • Extreamly reliable and robust.  Given the general lack of employees, I simply cannot afford for customers to call me to tell me that something is broken.  It has to work 24/7 without producing java stack dumps or IIS/.NET SQL/odbc error traces.    

  • Highly dynamic site – large portions of the content cannot be cached effectively and need recreating on every view.

  • Huge number of visits (probably not going to happen, but I can dream).

    •  
     

    Labels: , ,

    Posted by Joe Turner on Tuesday, October 2, 2007 at 1:02 PM |

    Hey, I (as Wt's main author) would be really interested in hearing whether, indeed, Wt lived up to its expectations, or, if not, what were the main problems you encountered ?

    Posted by Blogger Koen | October 18, 2007 5:29 AM  

    Post a Comment