The only issue perhaps is what happens when some bloak leaves this on in a production environment... do we stop logging or do roll-overs after some point, or what?
This strikes me as a sort of thing that could be configured dynamically. Some centrally accessible class, perhaps James, could have a variable:
public boolean per_message_logging_enabled;
This value, which would be tested before any per-message logging was done, could be turned on and off from an administrative interface while everything was running.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
