So far I can see you have multiple services that can call each other in random order and that is on design.
AFAIK each service is message based and are stand alone applications (either own process or own application domain). As each service will open its own connection to its (or the which I guess in your description...) database. If you have a service that is currently chatty because it needs to fetch details for an object array and be processed for a request / response model then I indeed understand that you want to remove chatty overhead as the obvious guess here is that your interfaces/contract need to be renewed to allow multiple request in one round-trip be processed OR don't use a request/response model. My guess is that your domain objects somehow have state that can affect other domain objects. Like bank accounts where ammounts flow between them and that you somehow need to read such data in the same transaction over multiple request thus having a session over a service thus a statefull service. Still... I don't see any problems with all those sessions for each service as it needs to protect the data it is responsible for. I think you are seeing problems that are not there or you are experiencing problems not caused by NHibernate. Ramon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
