Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Architecture> Simplest Way to add Application Layer
 

Pages: 1
Architecture
Simplest Way to add Application Layer
Page:1/1 

  Print all messages in this thread  
Poster Message
DaveR
User



Location:

Joined on:
15-Jun-2004 16:37:10
Posted:
43 posts
# Posted on: 23-Jan-2008 18:22:31.  
We have a Windows Forms application using LLBLGen 2.5 with SQL Server.

We chose the SelfServicing model, and make heavy use of the Entity, Collection and TypedView classes, including some custom code regions. Some of our business logic lives within the LLBLGen classes.

The one downside to this approach is that the Windows application communicates directly with SQL Server. Firewalls get in the way, and security becomes a concern.

We would like to re-architect the application so that the client does not connect directly to SQL; it should connect to an application layer via HTTP or HTTPS, i.e. via .NET Remoting or Web Services. And, we want to do it as easily as possible without having to rewrite a lot of code.

I realize it might have been easier had we chosen to use Adapter; then plugging in remoting or WCF might be straightforward. But we want to continue to use SelfServicing if possible, to avoid rewriting practically all of our data access code.

Is this a losing battle, or are there effective ways to introduce a middle tier using SelfServicing in LLBLGen 2.5?
  Top
jmeckley
User



Location:
Harrisburg, PA, USA
Joined on:
05-Jul-2006 16:03:19
Posted:
403 posts
# Posted on: 24-Jan-2008 14:01:16.  
SS needs access to the db. if you want a client disconnected from the database then you will need to migrate to the adapter model where entities are unaware of the database.



Jason Meckley
Programmer
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.