I'm considering to use NHibernate for a new Application. I'am familiar with NHIberante, but only with 1 User Application. So my challenge is to control concurrency
Before I start, i would appreciate to have some information, how Clients should communicate with the Server
The Application should run like this:
- The Application is used only in a LAN.
- Winforms
- SQL 2005
- DB is very Simple, about 10 Tables are mapped (1-n, 1-1) to one Table
- Multiple Access from 1-10 Workstations
- 90% is read-only, 10% insert/update
- concurrency may appear
Whats the best practise?
Communication with WebServices, .NET Remoting Services or directly to the DB with the app.config File from each Client?
Lazy Loading of course is important, because some Collections are very large (>10'000).
Thanks in advance
|