[commits] Horde branch master updated. 092128ca13af4e58906fa973711f914e7d08bb8a

[Jan Schneider]

The branch "master" has been updated.
The following is a summary of the commits.

from: dae30870b343a8e2973474a99edaaa6b01510e58

092128c Keep using the write backend, even for read operations, in the same request after writing once.

-----------------------------------------------------------------------

commit 092128ca13af4e58906fa973711f914e7d08bb8a
Author: Jan Schneider <jan at horde.org>
Date:   Fri Jun 3 18:48:16 2011 +0200

    Keep using the write backend, even for read operations, in the same
    request after writing once.
    
    This is a very simplistic approach to avoid stale data at least in those
    cases where we immediately read and cache away data after writing it,
    most notably in the share system.
    
    Other solutions are to:
    - use sql hints like http://www.php.net/manual/en/mysqlnd-ms.rwsplit.php
    - cache written data in the application that must not contain stale content.
    - configure a TTL for which a user who has just written data keeps using
      the master server.
    - use data versioning to decide how long to read from the master server;
      version could be in cache, db, or builtin (SHOW SLAVE STATUS).
    - ???

 framework/Db/lib/Horde/Db/Adapter/SplitRead.php |   20 ++++++++++++++++++++
 framework/Db/package.xml                        |    4 ++--
 2 files changed, 22 insertions(+), 2 deletions(-)

http://git.horde.org/horde-git/-/commit/092128ca13af4e58906fa973711f914e7d08bb8a