Re: Implementing a 3-tier client-server system
- From: "Tobin Harris" <tobin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 19 Jun 2005 23:08:08 +0100
Hi Mokles,
As josh said, you could just put your middle tier objects in a separate DLL
(or even just a separate namespace, if it's a small project). Setting up
remoting, a web service layer, or any other layer is going to be more work
of course - so I'd make sure I need it. If you can get away with having an
ASP.NET GUI layer referening your business logic DLL, then that's a nice
simple start IMHO.
Tobes
"mokles" <mokles@xxxxxxxxxx> wrote in message
news:ROqdnbEDxY2_DyjfRVn-vA@xxxxxxxxxxxxx
> All,
>
> We are trying to implement a 3-tier Client/Server Widows system in .Net.
> We have found that the middle tier can be implemented using Webservice or
> remoting. We are just wondering what other options we may have to
> implement
> the middle tier. Any help will he highly appreciated.
>
> Thanks,
> Mokles
>
>
.
- Follow-Ups:
- Re: Implementing a 3-tier client-server system
- From: mokles
- Re: Implementing a 3-tier client-server system
- References:
- Implementing a 3-tier client-server system
- From: mokles
- Implementing a 3-tier client-server system
- Prev by Date: Re: Dynamic Object Reference
- Next by Date: Re: Dynamic Object Reference
- Previous by thread: RE: Implementing a 3-tier client-server system
- Next by thread: Re: Implementing a 3-tier client-server system
- Index(es):
Relevant Pages
|