1. 24 Apr, 2009 4 commits
  2. 17 Apr, 2009 1 commit
  3. 15 Apr, 2009 1 commit
  4. 12 Apr, 2009 1 commit
  5. 11 Apr, 2009 1 commit
  6. 10 Apr, 2009 2 commits
  7. 31 Mar, 2009 1 commit
  8. 30 Mar, 2009 14 commits
  9. 24 Mar, 2009 1 commit
    • Jim Fulton's avatar
      Rewrote zeopack: · 1462cc9c
      Jim Fulton authored
      The zeopack script has gotten a numner of improvements:
      
      - Simplified command-line interface. (The old interface is still
          supported, except that support for ZEO version 1 servers has been
          dropped.)
      
      - Multiple storages can be packed in sequence.
      
      - This simplifies pack scheduling on servers serving multiple
            databases.
      
      - All storages are packed to the same time.
      
      - You can now specify a time of day to pack to.
      
      - The script will now time out if it can't connect to s storage in
          60 seconds.
      
      - It now has a test. :)
      1462cc9c
  10. 26 Feb, 2009 1 commit
    • Jim Fulton's avatar
      Bugs Fixed: · 4f5852a2
      Jim Fulton authored
      - Connections from old ZEO clients weren't discarded when they were
        closed causing memory to leak and invalidations to become
        increasingly expensive over time.
      
      - The monitor server didn't correctly report the actual number of
        clients.
      4f5852a2
  11. 21 Feb, 2009 1 commit
  12. 20 Feb, 2009 1 commit
  13. 17 Feb, 2009 2 commits
    • Jim Fulton's avatar
      Fixed bug: · 390c6148
      Jim Fulton authored
        Packing could return spurious errors due to errors notifying
        disconnected clients of new database size statistics.
      390c6148
    • Jim Fulton's avatar
      Fixed a serious bug: · 3fa58ce7
      Jim Fulton authored
        Packing a blob-enabled file storage in a ZEO server caused blob data
        to be lost.
      3fa58ce7
  14. 07 Jan, 2009 1 commit
  15. 05 Jan, 2009 2 commits
  16. 04 Jan, 2009 4 commits
  17. 03 Jan, 2009 2 commits
    • Benji York's avatar
      fix wrong adjective · 96a9be81
      Benji York authored
      96a9be81
    • Jim Fulton's avatar
      Previously, database connections were managed as a stack. This · caf606b0
      Jim Fulton authored
      tended to cause the same connection(s) to be used over and over.
      For example, the most used conection would typically be the onlyt
      connection used.  In some rare situations, extra connections could
      be opened and end up on the top of the stack, causing extreme memory
      wastage.  Now, when connections are placed on the stack, they sink
      below existing connections that have more active objects.
      caf606b0