Hello folks, i'm quite new to NHibernate and tried to find a hint to my problem in the faq and the forum but did not find anything.

I have a normal WindowsApp that -till now- uses the DataLayer with Castle and NHibernate as a DLL which is fine for single user access, but the next goal would be to configure and use it as a real multiuser service.
Unfortunately I have no idea how to implement that.

What would be the easiest way to gain a real IoC-Container and share it by mutliple clients? Do i have to use an Applicationserver? Is there a Walkthrough? Any hints appreciated.
Thanx for reading.

Hi,

I am not sure that the following is the best way, however I am using it in my situation ([NAME] are virtual/physical project assemblies) :

On the main Server:
[ DAL (NHibernate Classes) ] <-> [ BLL (Typed Actions - Save, Get, Delete for entities) ] <-> [ Facade (.NET Remoting Server/Web Service - exposes BLL Factory) ]

On other Servers:
[ SITE (User Interface - .NET Remoting Client/Soap Calls) ]

This assures that you have only one persistance layer and multiple clients.

OK, thank you but i have no idea how to do this. can you give a Link or something where i can see how to implement that. Maybe any of the "look were clicking some code"-Examples.

Or tell me. Is it possible to run a WindsorContainer for each Application just telling Castle that the DB takes care of synchronization? Maybe by setting the Transactions-Attributes or something. That would be the easier way to get rid of the damn problem without blasting my hed with all that .net remoting stuff.
thx, Joe

Joe,

If I understand correctly, your goal is to have a single application server where all of your business logic and data access will run. Each client would then hit this application server. Is this right?

If so, may I ask, what is your actual end goal? It's been my experience that remoting is a fine option for some situations, but just deploying the code to every client would be much easier. The database will still be a shared back-end and you can easily account for versioning and locking in your application (with NHibernate's help, of course!)... look at the Version and Timestamp attributes in the mapping for two possible options to help with obtimistic lock resolution.

On the other hand, if you're looking to seamlessly expose your services to a bunch of clients, then you might want to consider something like web services. Again, it really depends on what your end goals are.

BeeGone has a great suggest for how to consolidate things. Just learn more about .Net Remoting and Web Services and you'll find plenty of examples... The easiest way to handle either scenario is with the help of IIS and that'll allow you to continue to use Winsor.

Ben

First of all Thank you for your reply.


Yes, this was my first idea, but if it is possible to do it in an other way with optimistic locking i think regarding my poor knowledge of .net - remoting i would prefer this last solution.


This seems to be exactly what i'm looking for. As i mentioned this is the actual. Thank you for this Tip.


This would be a nice idea but for now the other strategy seems to be faster. I already learned a lot on remoting yesterday and it seems quite capable, but this would be a task some quiet and lazy winter day.
Alright. In the end, BeeGone and benhyrman, i have to say thank you to both of you.
JoeG.