Kpixel:
Thanks for your reply. I had performed a search on this forum and found that topic, but I felt it didn't answer my question - though, I realize, I may be asking it incorrectly...Let me elaborate a bit...
I'm working on an architecture proposal and need to have this main issue nailed down. I'm choosing to use Remoting over Web Services and Data Transfer Objects because I view it as extra and unnecessary work. Also, the platform is restricted to just .NET so interoperability is not an issue and, should it become one, we just implement the Web Services anyhow...To complicate matters, the library[ies] that will compose the business logic will need to run within COM+ to take advantage of object pooling and distributed transaction services.
This is the primary reason why I felt that post you referenced did not address my concerns as passing ISession/ISessionFactory instances to the client would, in essence, break the architecture. I still need to maintain lazy-loading capabilities, which is why I mentioned having the entities subclass a MarshalBy* object so that they can be transmitted between the client and server tiers thinking there was some "magic" that NHibernate does that allows the collections etc. to continue to load once they cross the process boundry...
If this is not possible my only option, at this point, is to propose migrating the existing home-grown O/R solution, which will be a significant effort. This architecture is something I would love to prototype, but at the moment, I don't have the time (or billing vehicle) to do so...
If anyone has any suggestions, I'm all ears and they are all greatly, greatly appreciated...
Thanks again!!!
|