Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> many such applications would be written with workarounds for
> broken serializable behavior, workarounds which would behave
> unpredictably after an upgrade.
Can you elaborate?
The techniques we use in our shop wouldn't interact badly with SSI,
and I'm having trouble picturing what would. Sure, some of these
techniques would no longer be needed, and would only add overhead if
SSI was there. They would generally tend to prevent code from
getting to the point where a serialization failure from SSI would
occur. In spite of that there would probably be at least some
additional serialization failures. What other interactions or
problems do you see?
-Kevin