Hi Rocky,
Quoting http://www.lhotka.net/weblog/OverviewOfCSLANET36ForWindowsAndSilverlight.aspx
"Mobile objects are an incredibly powerful technique for exploiting the power of object-oriented design and programming in distributed environments. The CSLA .NET data portal abstracts the complexity of this concept. The result is that your application can switch between 1-tier, 2-tier, 3-tier and even 4-tier models with no change to code - the change is purely one of configuration."
I searched the forum but found nothing about this subject. How would Csla work in 4 tier mode?
The CSLA .NET for Silverlight video series walks through the 4-tier deployment model end-to-end (http://store.lhotka.net).
But it is like this:
Silverlight client -> public web/app server -> private app server -> database server
The assumption is that you are doing this because you have two firewalls - one between the world and your public web/app servers, and another between your web/app servers and a set of internal app servers. A pretty typical web DMZ model.
The Silverlight data portal is designed so one option is to configure the data portal to run on the web/app server and act as a pass-through or router that relays the calls to the private app server. Before doing that, you do have the opportunity to examine the client request to decide if you want to allow it to proceed.
Thanks Rocky.
RockfordLhotka:
The CSLA .NET for Silverlight video series walks through the 4-tier deployment model end-to-end (http://store.lhotka.net).
But it is like this:
Silverlight client -> public web/app server -> private app server -> database server
The assumption is that you are doing this because you have two firewalls - one between the world and your public web/app servers, and another between your web/app servers and a set of internal app servers. A pretty typical web DMZ model.
The Silverlight data portal is designed so one option is to configure the data portal to run on the web/app server and act as a pass-through or router that relays the calls to the private app server. Before doing that, you do have the opportunity to examine the client request to decide if you want to allow it to proceed.
CSLA .NET for Windows doesn't provide a router component like it does for SL, but you can create your own pretty easily.
The data portal is all interface-based and uses a provider model. So you can create a custom host that does nothing but relay the client call back into the data portal - thus acting as a relay/router on the public server.
Copyright (c) Marimer LLC