Well, instead of writing glue code and wondering (for example) how to encapsulate the usage of booster::shared_ptr or pondering over ownership questions/issues if I transfer the pointer to a boost::shared_ptr, I'd prefer cppcms API to use boost-original.
I'd compile the library myself, anyway, which relieves me of the ABI troubles.
My current stable version of CppCMS uses boost in its API and relays on boost-signals, boost-iostreams, boost-system and boost-regex. Have you tryed to deploy such library to remote host? I think you hadn't? Even I'm myself, had huge troubles deploying hotfix to production server that was running cppcms because the production server had different version of boost. And both servers were under my total control... Such dependencies are very critical. Especially for CppCMS uses that have great headaches deploying their applications to other environments. For next version it would be much simpler. As it today simple for KDE, Gnome, GTK or Qt based applications. Artyom