That all depends on the use case, and the requirements but yes in General I agree this should exist in a transaction and I am not sure why I've not done this. So now where to control the transaction, I like how right now my web has no concept of the data (outside of the httpmodule that ensures the session is closed). It just takes a high level "Service" which then uses a dao to perform the nHibernate functionality. I'd hate to make the assumption that my Service controls the transaction...since you might want to have two services cordinated in a single transaction.
I'm struggling with finding a good pattern here that controls transactions at the appropiate level, without leaking nHibernate to my web...any thoughts? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
