Comment 6 for bug 1592238

Armando, I don't see why you characterize this as "tight coupling" when the intent is, as I understand it, for the same MD to both supply (in precommit) and consume (in postcommit) the driver-specific data. And precommit and postcommit cannot generally be combined into one method, since precommit is guaranteed to be inside the transaction and postcommit is guaranteed to be outside it. It is very common for MDs to implement both these methods since they need to do certain things within the transaction and other things outside it after it has committed.

I agree state can often be retrieved or recreated in some other fashion, so this may not be a critical requirement. But I would hate to see MDs resort to just adding random properties to the Context class and then breaking when ML2 changes internally.