> > I've been heading this way in the patches I do - building single > functions that obtain just the right amount of data, sliced or not, > with various attributes calculated (or not) - but its very hand craft, > rather than introspected and code-generated. > > Another thing that would be nice is to pipeline stuff - to turn DB > access /off/ during the render stage, so that we don't have any > unpleasant performance suprises (and we could even, in principle, move > to a multicore model there, if we weren't using python :P) > > This is also similar to the threads about separating persistence from > business logic, which may be a supporting change. >
I'd go so far as to say that the two improvements listed above (which should be core to any ongoing improved architecture/infrastructure work) are only really practical on a wider scale if the separation of persistence from business logic is done. That is to say, my view is that the separation is more than just a supporting change, it's almost a pre-requisite to be able to execute the other changes with the quality and velocity required. Just my 2c _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
