…preference is not primary or secondaryPreferred (primary is the default and secondaryPreferred is already covered by slaveOk bit).
…ed the increase is from the value used by the superceded Mongo class.
…lica set have been found that match what was requested
…ongoClientOptions instead of MongoOptions. So the job of setting the default writeConcern is now delegated to MongoClientOptions instead of handled explicitly by MongoClient
…so as not to break clients that are mutating that instance before passing the MongoURI to a Mongo constructor
…re, authenticate to the admin database
…URI, automatically authenticate the database. This is done lazily on first use of the database by just setting the credentials on the DB instance. Care is taken to make sure that DB.authenticate and DB.authenticateCommand still work correctly even if credentials are on the URI, so long as the same credentials are used in all cases. Otherwise clients who were working around this by calling those methods explicitly would break.
…nd MongoClientURI, all of which have a default write concern that waits for acknowledgement of the write from the server. MongoClient extends Mongo so that it's easy to switch to it just by changing which class is constructed. MongoClientOptions, unlike MongoOptions, is immutable and has a static inner Builder class for construction.
…e for all the timeouts in ReplicaSetStatus, MongosStatus, and DynamicConnectionStagtus
…his issue. In the case where the driver is not connected to a replica set, like in mongos HA, still may need to ensure there is a master
…nt people to MongoOptions.alwaysUseMBeans property
…tionPool and Java5MongoConnectionPool. The former is an MBean and the latter is an MXBean. When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine. This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).
…ely-called method, to avoid having it called more than once. Protected OutMessage by setting the buffer to null and checking for null everywhere it's used.