Ariel Popovsky
10/27/2004 7:58:00 PM
Hello Brian,
Perhaps you don´t need to use CAO, if your business objects are just data containers you can call a method on a SAO object (the data access layer) that creates the instance of a serializable BO and returns it to the caller.
-----
Ariel Popovsky
> Hello All,
>
> I've been given the task to redesign a .NET application. The idea is
> to have all the the business objects on a remote server, which can be
> access by .net remoting by several websites.
>
> My question is a design question (and basic understanding :):)). I
> designed my classes to be a container of information. What that means
> is the class will have properties and several overloaded constructors
> with parameters. The constructors contain methods that populate the
> properties depending on the values of the parameters. So what I want
> is the ASPX pages from my website to use .net remoting and create a
> new instance of a remote object and access the instance's properties
> and methods. In other words, use it like a regular instance of a
> class.
>
> After reading several sources and scanning the newsgroup, I decided
> that CAO will be the way to go since I need to pass parameters to the
> constructors. But the impression I get from all the .net remoting
> examples (whether CAO or SAO) is that they only call methods from a
> remote class. So in other words, you don't really use the remote class
> as a container of data, but as a vehicle to call a method remotely.
>
> In other words, am I using .net remoting the wrong way?
>
> Thanks in advance,
>
> Brian
>
> P.S. If you require more detail, please let me know.
>