I lean towards the net effect that Geof proposed of not saving the file, removing the session from memory, and logging the exception so that the admin can follow up. Does this meet our needs adequately?
Could we solve this by using the app._exceptionHandlerClass(app, None, excInfo)? The transaction would be passed as None, because there is no current transaction while saving a session to disk. The ExceptionHandler class looks like it is already designed to handle a non-transaction oriented exception. This would log the exception normally, and e-mail if configured to do so. I would probably implement a suitable accessor function, perhaps Application.handleException(excInfo) which would be similar to handleExceptionInTransaction() but of course use None for a transaction. Although we could possibly get away with calling handleExceptionInTransaction() with transaction=None. Was this what you meant by the logging module? Or were you referring to the new logging module coming in python 2.3? -Stuart- ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
