Re: Implementing a 3-tier client-server system

Thanks Tobes.
Your explanation helped a lot. Now I have to find out if remoting or web
services are the only options I have if I want to have a dedicate middle
tier server.

Thanks again.
Mokles

I have to explore this little
"Tobin Harris" <tobin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42b88766$0$20983$db0fefd9@xxxxxxxxxxxxxxxxx
> Hi Mockles
>
> Usually the n-Tier refers to logical tiers - meaning layering in the
*code*.
> For some projects, it's perfectly acceptable to put all your tiers on a
> single server. I'm no expert on this, so perhaps others can advise.
>
> Other ways of scaling are to have your GUI and business logic on one
server
> and the database on another. You could create a dedicated middle tier
> server, but then you'll need to consider mechanisms such as remoting or
web
> services to allow this tier to be used by other processes on other
machines.
>
> It usually makes sense to put your data as close to your application as
> possible, and also sense to give your business layer fast access to your
> data. I suppose it depends on how big your application is as to where you
> create physical separations.
>
> Tobes
>
> "mokles" <mokles@xxxxxxxxxx> wrote in message
> news:GsudneAJGLxtoCvfRVn-tg@xxxxxxxxxxxxx
> > Thanks, Tobes and Josh for the reply.
> >
> > Just to make sure that I understand, after building the middle tier
> > objects
> > into DLLs I have to put them on a machine (called Application Server?).
> > Then
> > from my Front End project I have to create a reference to the DLLs on
the
> > Applicaion server and use the DLL in the Front End project. I am
assuming
> > that the Application Server and the Front End appliction project will be
> > on
> > the same Windows domain. I will try this out.
> >
> > Thanks again.
> >
> > Mokles
> >
> > "Tobin Harris" <tobin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:42b5ecc9$0$4095$db0fefd9@xxxxxxxxxxxxxxxxx
> >> 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


.

Relevant Pages

  • Re: Implementing a 3-tier client-server system
    ... Other ways of scaling are to have your GUI and business logic on one server ... You could create a dedicated middle tier ... services to allow this tier to be used by other processes on other machines. ... > Applicaion server and use the DLL in the Front End project. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • RE: C++ Garbage Collector on VMS?
    ... And HW is usually not a problem in th app tier. ... One for App server, one for DB. ... Tiers were a great concept when HW could not keep up with the processing required by each tier and network speeds were slow and unreliable. ... In small to medium app environments, ...
    (comp.os.vms)
  • Re: n-Tier development
    ... What does it change when I communicate on whatever line to a middle Tier ... how small it is and what protocoll to detect if it is for the right client ... [App Server ] ... >>> pooling and stuff like that you'll need to run them in IIS or Windows ...
    (microsoft.public.dotnet.general)
  • Re: US military and confidentiality
    ... The first tier receives ... quotation information from SuperMontage's Hewlett-Packard Non-Stop ... running on Windows 2000 Server and SQL Server ...
    (comp.os.vms)
  • Help popping a web application
    ... the OS/Network/ or server system itself. ... Web tier: Web Server is IIS 5.0, ... URL rewrite for bypassing any login type criteria- no joy ... No information in the html code. ...
    (Pen-Test)