Hi all, I'm trying to get an indication of the best way to isolate work between my web service's various request threads, so they don't step on eachother's toes.
My ISession is persistent across all web service calls. Currently, I'm creating a Transaction before doing any of the web service's work, then submitting that transaction when it's complete, but I'm not confident it's isolating the work the way i'd expect. -- Is this the correct way to go about this, or should i aggressively lock entities? ---- My only worry with locking entities in one web session, is that i'll be impossible to unlock them in the subsequent session (or that a new web service call will unlock an entity it's not supposed to) -- Should I create a child Session? ---- my only worry here is that I don't want to have to re-query the database any more than I have to. the singleton Session instance is providing me with this benefit. II can't seem to find a best-practices guide to isolating units of work - so if documentation exists somewhere and I'm just not seeing it, I'll take it as a starting point. TIA ------ Joe Brockhaus [email protected] ------ -- 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.
