Get More Support

Here for you 24/7

learn more
VOD Free SDK

Start Building your Engine Now

Download Now
VOD Extranet

Access to patches, license management,
tech docs and more for existing VOD customers.

Learn More
Db4o and multi-threaded behavior
Last Post 18 Oct 2011 12:49 AM by agalica. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
agalica
New Member
New Member
Posts: 36


--
13 Oct 2011 04:30 AM

    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?

    Patrick Roemer
    Advanced Member
    Advanced Member
    Posts: 640


    --
    17 Oct 2011 05:55 PM
    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.
    agalica
    New Member
    New Member
    Posts: 36


    --
    18 Oct 2011 12:49 AM
    Excellent answer, thank you.
    You are not authorized to post a reply.


    Active Forums 4.3