Replace use of type('') with basestring.

The code didn't call setLocalTransaction(), so getTransaction() always
did the same thing as transaction.get().

essentially means a connection keep track of which objects from
the connection are modified, instead of transactions keeping track of that.
A good consequence hasn't yet been implemented:  if a connection is
closed with modifications still pending, we can detect that efficiently
now, and complain.

again

Add comment about use (or lack thereof) of classFactory in Zope.

application; needs work, but this should get most projects going

- add discussion of the issues surrounding keys and multikeys with
  name="+" and default values

the deprecation warning for setLocalTransaction().

This changes the behavior slightly for invalidations.  A Connection
will receive invalidations even if it didn't have any modified objects
in the transaction, e.g. db.undo() or a read-only transaction.  For
this to work, it assumes that the thread that called db.open() is the
thread that is going to use the connection.  If this isn't true, the
synch argument to db.open() can be used to disable the new feature.

note the different default hostname for an inet-address on Windows and Unix

ZServer package.

aren't needed any more

is an API shim to the logging module.  No more competing initializations!

implementation.  The configuration aspects of zLOG are about to disappear.

can import just one of eventlog and logger if desired.  This is needed for
Zope 2 to allow the main Zope configuration to only use eventlog, since the
name "logger" is used for something else.

think they're allowed to do it.  For now, just let zLOG initialize
everything; we can figure out the right way to make zLOG and logging
co-habitate later.

- don't dump everything into the "event" logger;
  use the subsystem argument to zLOG.LOG to get a specific logger
- move some comments into docstrings