-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Best practice for a new application
PostPosted: Mon Dec 04, 2006 4:58 pm 
Newbie

Joined: Fri Dec 01, 2006 11:36 am
Posts: 6
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


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.