Managing detached objects in a long running desktop application is kind of a pain, mostly because you can have several instances of the same entity (one per session instanciating it). Second level cache is great for not rehitting database, but it only store entity values, not entities objects, like first-level cache.
I'm brainstorming about the idea of a cross session first level cache. It would allow multiple sessions to return the same instance of data. It could use weak references so that unreferenced entities would be reloaded. Does this kind of cache exists? If not, I guess it am not the first one to have this idea. Would that be a bad one? Or a very hard to implement one? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
