Artyom wrote:
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?
I do that almost every Wednesday around noon with about 100 libraries, not kidding :-)
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...
Boost is part of the deployment. Thus, I can always rely on having the right version. Regards, Roland