Forums

I understand that db4o has thread safety (i.e. threads won't trample upon each other), and my ultimate understanding is that db4o is natively single-threaded in its behavior, so it can only ever handle a single request at once.

However, in response to an answer about a db4o query on stackoverflow (http://stackoverflow.com/questions/...eriences), someone stated that the threading model in CS mode is different.  Is this true?  Or do clients in a CS model still have to wait for other clients to finish each request?

The db4o core is single-threaded, indeed, so whenever a message from one client is processed on the server, others have to wait. However, C/S clients queue messages and state locally until they require a response from the server or until they have reached a commit sequence point, then send a batch message to the server, thus reducing C/S roundtrips and, indirectly, server contention. Probably that's what the 'different threading model' refers to.

Excellent answer, thank you.