Re: [dev] RFC IMVCCStorage everywhere (Move ZODB's MVCC to storage layer)
Jason Madden <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <[email protected]> |
> On Jun 16, 2016, at 09:43, Julien Muchembled <[email protected]> wrote: > > Generally speaking, I find the whole result more complex than just seeing Connection code calling methods directly on the real storage, and if the storage does not overload, look at the inherited mixin. I'm of the opposite opinion. I find the new code to be substantially simpler than before with a much better separation of concerns. Want to see how MVCC works? Look at one file. Want to see the logic flow of a Connection and how it interacts with any storage? Look at one file. I too generally prefer composition over mixins. I often find the result simpler to understand because the pieces are smaller, and easier to adapt and evolve for the same reason. As for the extra indirection of a method call...well, any JIT worth its salt will optimize those away :) Jason -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.