"The NH cache is for objects retrieved by NH" I understand that. What confuses me is that somebody wrote an API to take things out of that cache without writing an API to put things into it.
Why allow the ability to take something out of that cache? Somebody had justification for writing such a function back in the day. So, isn't that same justification viable for a reason to be able to stuff something into that cache? Even better yet a SessionFactory.Replace(object) would be perfect, because I just need to take the new copy of Object A and overwrite the old Object A and have that new Object A be the master. "If you are getting it from other source, you can cache it yourself using the same underlying cache (syscache, memcached, etc)" I'm not sure what you mean. Are you saying there is a way to stuff an object into the L2 cache? If so, how do I get at the SessionFactory's underlying memory structure that is used to implement that cache? Or, are you saying that I should implement my own cache, separate from SessionFactory? In that case, what good would it do, because SessionFactory wouldn't be aware that I have a separate cache where it could find objects instead of selecting them. Thanks for your help. Hugh -- 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.
