1. 19 Jun, 2004 1 commit
  2. 12 Jun, 2004 2 commits
  3. 09 Jun, 2004 1 commit
  4. 04 Jun, 2004 3 commits
  5. 03 Jun, 2004 2 commits
  6. 02 Jun, 2004 2 commits
  7. 30 May, 2004 1 commit
    • Chris McDonough's avatar
      - "Bucket finalization" is now done more aggressively. Instead of waiting · d62a0d18
      Chris McDonough authored
        until a bucket is garbage collected (which may be much later than the
        expiration of that bucket), we "finalize" a bucket as soon as possible
        after it gets expired.  This effectively means that the "delete notifier"
        will be called much closer to the time that a transient object actually
        expires.
                                                                                      
      - Add a "_last_finalized_timeslice" counter; this counter keeps track of 
        the bucket which was finalized last.  Set the initial value of
        "_last_finalized_timeslice" to -period; this services the unit tests for
        finalization, where there can actually be a timeslice that is 0 and we 
         need to finalize that bucket.
                                                                                      
      - Add a series of locks to prevent finalization, replentishment, and
        garbage collection from being attempted by more than one thread
        simultaneously.
                                                                                      
      - Add "Fake" module for interactive testing purposes (swap out BTree for
        simpler object during stress tests for isolation purposes).
                                                                                      
      - Allow DATA_CLASS to be specified (this is the main data structure
        class).
      
      - Update docs and tests to account for new finalization strategy.
      d62a0d18
  8. 29 May, 2004 4 commits
  9. 28 May, 2004 13 commits
  10. 27 May, 2004 6 commits
  11. 26 May, 2004 3 commits
  12. 23 May, 2004 2 commits
    • Chris McDonough's avatar
    • Chris McDonough's avatar
      Merge from 2.7 branch: · 1eeff781
      Chris McDonough authored
      Collector 789:  Zope's transaction behavior flawed.
                                                                                      
      Historically, errors that made it up to the publisher have run outside the
      context of a transaction.  This has caused problems for applications which
      expect to be able to write to the database (if only temporarily, before
      transaction.abort() is eventually called).
                                                                                      
      With this patch, we allow the error to execute in the same transaction as
      the "main" request, and abort only after the error has executed.
      1eeff781