[Subversion] / PEAK / CHANGES.txt  

Diff of /PEAK/CHANGES.txt

Parent Directory | Revision Log

version 1700, Fri Feb 20 15:24:21 2004 UTC version 1751, Fri Jun 4 17:02:55 2004 UTC
Line 1 
Line 1 
 Fixes and Enhancements since Version 0.5 alpha 3  Fixes and Enhancements since Version 0.5 alpha 3
   
  - Added 'ref:factory@addr' URL scheme that maps to a corresponding   - The 'log()' method of PEAK loggers ('logs.ILogger') now accepts a level name
    'naming.Reference("factory",["addr"])'.  'factory' can be either a dotted     *or* a number, for convenient invocation.
    import string referencing a 'naming.IObjectFactory', or you can define  
    a factory in the 'peak.naming.factories' property space.   - SQL transaction semantics have changed.  Now, issuing an SQL statement
      *always* causes the connection to join the active PEAK transaction, even if
      you request that the SQL be issued "outside" a transaction.  Such SQL will
      be issued outside of the *database* transaction, but not outside of the
      PEAK transaction.  This simplifies the overall processing model for dealing
      with "untransacted" SQL such as Sybase DDL or read-only Oracle transactions.
      (In particular, the requirement that triggered this change was to allow
      Oracle read-only transactions to be released at the end of the current PEAK
      transaction.)  Also, got rid of the now-meaningless 'begin' command in n2.
   
    - The 'events.IEventSource' interface now returns a 'canceller' function from
      the 'addCallback()' method, allowing you to cancel a previously-scheduled
      callback.  This fixes a memory leak and performance problem with
      'events.AnyOf()', which previously could accumulate unneeded callbacks on
      the sources it was monitoring.  Note that if you have developed any custom
      event sources with 'addCallback()' methods, you must make sure that they
      return a canceller from now on.
   
    - Added 'ref:factory@addr1||addr2' URL scheme that maps to a corresponding
      'naming.Reference("factory",["addr1","addr2"])'.  'factory' can be either a
      dotted import string referencing a 'naming.IObjectFactory', or you can
      define a factory in the 'peak.naming.factories' property space.
   
  - Added a 'zconfig.schema' factory, so that 'ref:zconfig.schema@streamURL'   - Added a 'zconfig.schema' factory, so that 'ref:zconfig.schema@streamURL'
    will load a schema loader.  Schema loaders are themselves object factories,     will load a schema loader.  Schema loaders are themselves object factories,


Generate output suitable for use with a patch program
Legend:
Removed from v.1700  
changed lines
  Added in v.1751

cvs-admin@eby-sarna.com

Powered by ViewCVS 1.0-dev

ViewCVS and CVS Help