Added browser_id_manager, session_data_manager, and temp_folder to list of application object's reserved names (making them undeletable).

Added session_data to list of temp_folder's reserved names.

timeout of default session_data container.

Improved error handling and logging of errors during the creation
of a transient object container.

The help version of TransienceInterfaces.py wanted to import Interface; it no longer wants to do so.

Changed interfaces files to reflect getContainerKey.

Specified permissions in helpsystem interfaces for transient objects.

Added proxy roles to the guestbook example, too. Also added a note about the proxy roles to the file library and guest book pages.

Fixed the management screen table. Now this management screen looks normal. Before it had strange margins.

Added a 'manager' proxy role to the filelibrary upload script. This should solve an authentication problem that Chris M was seeing. It also makes more sense in the context of this app.

As per suggestions by Amos, I changed the terminology used by the browser id manager and session data manager.  Previous to the change, browser ids were known as "tokens".  I've changed this to "browser id" in the docs as well as in all API methods that used the name "token".  Interfaces, permissions, and help have been updated with the changes.

 - Try harder to reduce global side effects in the 'createDB' bit
   (note that this piece of ugliness is due entirely to the hardwired
   dependency on FieldIndex &c in ZCatalog's ctor;  this should *go
   away*!


 - Move security manager handling to setUp/tearDown, to ensure exception-
   safe cleanup.

Added examples to Zope. Finally Zope comes with some simple example applications. The current examples include automatic navigation devices, a guestbook, a file library and a shopping cart. The examples make use of new features including ZPT (including macros) and sessions.

I set things up to automatically create an Examples folder in the root if one doesn't already exist. I don't know if this is the right thing to do or not. Maybe folks should have to add examples from the product add list.

If you would like to contribute example applications just let me know. I'm open to contributions.

Caused conflict errors to be counted at log time; additionally bumped severity back up to INFO for conflict logging, but caused conflict tracebacks to be logged at BLATHER.

  and ignored the user settings