Ciao John, On Wed, Jul 21, 2010 at 10:33 PM, John Davidson <[email protected]> wrote: > From what you are describing, NHibernate does not seem to be a candidate > part of your architecture. NHibernate is only designed to work with multiple > threads where those threads are unlikely to update the same entity instance > and when the _occasional_ collision does happen it is resolved by throwing > an error on one thread, notifying that thread that it failed.
I see. > It is not easily possible with NHibernate to load an entity instance in one > thread, then use that instance to fire new threads and update the instance > from the new thread. It may be possible if the first thread evicts the > instance before the new thread tries an update and the new thread performs a > read before the update. Sound very messy. Yes, very messy. Anyway, debugging on and on, I could see that the big deals are in *reading* data. > A cache like Microsoft AppFabric, formerly Velocity, may make this possible > with NHibernate, but that is a very specialized application of the > technology (not usually attempted by an individual who does not have > experience with all the tools involved). Thanks for the suggestion. By the way... what about a IStatelessSession? thanks again, Giulio -- -- 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.
