On 28 Sep, 2009, at 11:18 , Remy Blank wrote:
Hi Christian, Remy > Christian Boos wrote: >> But we can think about alternatives. For example, having a thread >> local >> cache for model objects which could make the retrieval of an already >> instantiated object from its resource cheap. Other ideas welcomed. > > Yes, I had the same thought after implementing the new cache > infrastructure on trunk. We should have some kind of per-request > cache. > I'd rather use the Request object for that, though, instead of a > thread-local. That way, it gets automatically discarded at the end of > the request. I'd also would like to rationalize the cache usage, it is now a very much localized approach, in some places (like the PermissionCache) only partial information are stored, adding data to the request sounds reasonable (and in Agilo we already do so, it might be a chance to make things right once and for all :-) ). The option of using the ITicketManipulator is too far away from the model, as you know in Agilo we do change tickets in many ways (and not only in Agilo) think at the import from CSV, or the Digital Whiteboard... or even the Backlog. A lot of third parties do the same. I really feel that permission control should be more close to the model, and there must be a way to make the permission checks on model property, this is just a thought. I know Trac it is far away from being there now, but still we could start moving things in the right direction... :-) > -- Remy ANdreaT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
