I've been thinking about this too. The main problem would be making it easy to extend.
The traditional HTTP side of it is trivial (just use nginx or something like that.) For template engine you have already Clearsilver and it's the fastest that I know of by an order of magnitude.
The key is solving how the application's developers could extend the web application. You can't expect them to code in C++ and compile every little change to their site. That's the beauty of CMF systems like Zope, you can put plain Python code in there with pages and components.
Doing a CMF in any lower level language and having to switch to a higher level language VM for every snippet would kill your original performance savings.
Find an element to fix that and you'll have a strong new contender in the CMF arena. Stuff like OpenMP and all that comes bundled in the new C++ libraries, transparently.
(BTW IMHO don't even think of starting without memorizing the Essential C++ books and all it's need-to-know patterns.)
The traditional HTTP side of it is trivial (just use nginx or something like that.) For template engine you have already Clearsilver and it's the fastest that I know of by an order of magnitude.
The key is solving how the application's developers could extend the web application. You can't expect them to code in C++ and compile every little change to their site. That's the beauty of CMF systems like Zope, you can put plain Python code in there with pages and components.
Doing a CMF in any lower level language and having to switch to a higher level language VM for every snippet would kill your original performance savings.
Find an element to fix that and you'll have a strong new contender in the CMF arena. Stuff like OpenMP and all that comes bundled in the new C++ libraries, transparently.
(BTW IMHO don't even think of starting without memorizing the Essential C++ books and all it's need-to-know patterns.)