Original MongoDB C + + driver partial problem solution (MongoDB C + + Driver)

This article gives me some problems and solutions for developing and modifying MongoDB C + + driver for a long time.
At present, the related engines introduced in this article have also released the closed source version, please download it yourself

Library version and related location: http://code.google.com/p/mongodb-cpp-engine/

Q & A
1. C + + version driver do we need a separate package?
A: Not necessarily to do this kind of behavior, but if we increase and use a connection pool its stability will be far better than we think.

2, the C + + version of the driver in addition to the official version, what version is there?
A: currently unknown, but I have completed a thread-safe version of: http://code.google.com/p/mongodb-cpp-engine/

3. What if the official C + + driver for MongoDB is used in multi-threading? Is it thread-safe?
A: There will be a lot of data confusion and the problem caused by the scramble for resources, such as recv when the packet is too large and other anomalies.
It is also clear that this version of the library is non-thread-safe and should be used with special care.

4. Does MongoDB need to process data asynchronously when server-side development?
A: Not required for the time being, according to my other article, data that is basically within 1 million does not require special processing and performance does not degrade.

There are other questions welcome to add

Collected in 2012-06-20

Original MongoDB C + + driver partial problem solution (MongoDB C + + Driver)