Re: ZODB with Lazy evaluation / Caching / Data Flow programming

Thank you Jim for the excellent answer. The ability to 
update remote user interfaces sounds very interesting indeed. 


Baron, welcome to the ZODB community.  I am curious what you re building?
What is the context for this question?  Or is it a top-secret startup?

In particular what are your transactional requirements?  Is this application running on multiple computers?   Do you want to store the objects in the database, but have the calculations only be in RAM?  What about consistency across computers?  

Jim, please correct me if I am wrong, but here is how I believe that the ZODB works.  If both ZEO clients are reading a value, no problem.  If both are writing a value, one is first, its write completes, the other computer gets an error.  But if one is reading, while the other is writing, but before the cache is invalidated, the read goes through.  Even though the data is a bit out of date, it is not a problem in most cases.  Jim, is that a correct understanding? 

If that is the case, Baron do you need to make sure that no other server has recently updated a value?  How do the distributed dependency relationship graphs handle this problem?
 
Warm Regards
Chris



-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.