Audit all event handling code in Crucible

XMLWordPrintable

    • Severity 3 - Minor

      Specifically, ensure events are fired after a transaction has been successfully committed.
      This ensures:

      • Listeners will have no chance of preventing a commit during the handling of an event
      • A Listener will always see data that has been successfully committed

      The current pattern in Crucible is to fire the event, and then commit the transaction.

            Assignee:
            Unassigned
            Reporter:
            Nick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: