Re: n-Tier development
- From: "CMM" <cmm@xxxxxxxxxx>
- Date: Mon, 30 Jan 2006 15:57:20 -0500
"Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:egVsXQbJGHA.916@xxxxxxxxxxxxxxxxxxxxxxx
> CMM,
>
> I see that you have well thought about it. However trying to get you out
> of a loop you are in my idea in (or maybe I am in it and can you show me
> that).
>
> What does it change when I communicate on whatever line to a middle Tier
> DataServer or direct to the EndDataServer?
When you communicate with the middle tier you're sending a
dataset-wth-changes in one network call over the LAN. This translates into
exactly two broadcasts (1 there, and 1 back.... a rountrip) no matter how
many records are in the dataset.
vs.
When you communicate with the data server directly you're sending sql
insert/update commands over several network calls. For instance, submitting
10 changed rows causes 20 broadcasts across your LAN.
It's as simple as that. Coupled with that fact that your LAN is used for
many other things (web, e-mail, etc.)- not just your app- I think the first
solution (3-tiered) is always the more efficient. It doesn't make much
difference with just a few users... but it also doesn't hurt much either!...
and it makes your app a lot more robust and easier to maintain in the
long-run.
.
- References:
- n-Tier development
- From: Steve Barnett
- Re: n-Tier development
- From: CMM
- Re: n-Tier development
- From: Cor Ligthert [MVP]
- Re: n-Tier development
- From: CMM
- Re: n-Tier development
- From: Cor Ligthert [MVP]
- n-Tier development
- Prev by Date: Saving Checkboxlist settings in VB 2005 for Each user.
- Next by Date: Re: n-Tier development
- Previous by thread: Re: n-Tier development
- Next by thread: Re: n-Tier development
- Index(es):
Relevant Pages
|
