Access work over a WAN

A

al

a piece of instruction before we go forward. networks
(both lan and wan) have two characteristics that we have
to take into account. the first is the 'bandwidth' or
speed of the path, the second is 'latency' or how long we
wait for some resource in the path. lan's have generally
high bandwidth and low latency, wan's have generally have
low bandwidth (as compared to a lan) and very high
latency. think of bandwidth as your speed on a highway and
latency as tollbooths. changing the speed limit from 30 to
60 when you have a toll booth every quarter mile buys you
nothing.
where are we going with this conversation ?

sloppy calls (i.e. inexact parameters, and not using
stored procedure calls) put you into the toll booths more
often, so faster links are a significant waste of money.

you can consider using 'thin-clients' but on the average
the increase the cost of bandwidth by a factor of ten
(i.e. client-server uses 2Kbps per active user, thin-
client uses between 10Kbps and 20kbps). it's all in where
you want to spend your money; good clean queries or sloppy
programming.

al
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top