mentioned prominently enough elsewhere...

Got rid of sys.exc_traceback, _value, _typpe references.

rather than the beginning of the next one.

Made minor optimizations.

MANAGE_TABS_NO_BANNER>" to provide a way for the manage_tabs user to
only get the tabs, nothing else.  (Useful for using the views/tabs
mechanism in other than management-interface applications.)

list. This caused all errors to use the root-level standard
error message.

proper URL of objects using the 'Find' machinery.  This caused all the
objects to mysteriously disapear when you updated the catalog (because
their paths were wrong)

  (in order to enable REMOTE_USER mode) also opens the monitor to any
  user connecting through localhost.

generates a hope-fully informative error if somebody tries to
use the utility with a file that is not a bobobase (ZODB 2) file, they
get an error message. A number of people have been trying to use bbb.py
with ZODB 3 file storage files.

peoprtysheet permissions are set correctly.

I could have sworn I checked this in before.

	  contained many version commits.

	- Database packing generated spurious error logs indicating
	  that there were bad references for objects created in
	  ncommitted versions.

so that we can map permissions of explicit acquirers.

as well as unusable with ZODB 3.

Changed HTTPServer, PCGIServer and FTPServer to override Medusa's listen queue limit under NT. This should drastically improve ZServer's performace on NT under heavy loads and should prevent refused connections under most circumstances.

less sloppy and unforgivving acquisition to fail when looking up
attributes of factory dispatchers.

based on profiler data.

when trying to get attributes during acquisition.  For example, it was
common for acquisition to mask errors occuring when trying to load
object state from the database, since this is typically triggered by a
getattr call.  I wanted to do something like:

  try: foo.bar
  except AttributeError, v:
    if v != 'bar': raise # Bogus attribute error
    # keep looking up the acquisition tree

Unfortunately, this fails because v is (sometimes) an
instance, not a string.

For now, we'll check for attribute errors, but ingore the values.