hello_server 13.2 -> 4.6 s / 8.1 -> 3.7 s
Just for the record, do you understand how ridiculous these times are for a "hello world" style of programm? For example here is a compilation time of a small "message board" that supports, users, sessions, localization, database, templates and more cppcms/git/examples/message_board/build$ time make -j 12 .... real 0m0.585s user 0m2.088s sys 0m0.406s cppcms/git/examples/message_board/build$ time make -j 1 ... real 0m2.319s user 0m1.936s sys 0m0.378s And here is amount of work: ] Generating simple.cpp [ 18%] Building CXX object CMakeFiles/simple.dir/simple.cpp.o [ 27%] Linking CXX shared library libsimple.so [ 27%] Built target simple [ 36%] Building CXX object CMakeFiles/mb.dir/apps/forums.cpp.o [ 45%] Building CXX object CMakeFiles/mb.dir/apps/main.cpp.o [ 54%] Building CXX object CMakeFiles/mb.dir/apps/master.cpp.o [ 63%] Building CXX object CMakeFiles/mb.dir/apps/mb.cpp.o [ 72%] Building CXX object CMakeFiles/mb.dir/apps/thread.cpp.o [ 81%] Linking CXX executable mb [ 81%] Built target mb [ 90%] Generating locale/he/LC_MESSAGES/mb.mo [ 90%] Built target create-mo [100%] Generating mb.db [100%] Built target sqlitedb ---------------------- The numbers you have shown are enormous especially when compared to alternatives It makes no sense to put everything related to http to C++ headers.
Artyom, on static polymorphism: the business logic doesn't have to be templated. Handlers are plain functions and can live in your own .cpp
Do they interact with taar::session::https session? extract information about
inputs, parameters, query string etc? if the don't/... what the session is doing - wrap it with something else ? How do you extract various information Once again, it is design question and separation of concerns Best Regards, Artyom