FBO's and WiFi

"Pete Zaitcev" wrote in message
news
This depends on how big the data piece is relative to the
starting handshake. Consider that TCP start-up involves
so-called 3-way handshake, and that many protocols have
a setup phase when client and server exchange messages
strictly in simplex, before bulk data transmission can commence.

Regardless, that still only affects the initial delay in response. Even if
the delay were 10 seconds (which it's almost never going to be), that's in
the same ballpark as the delay some servers have just getting around to
servicing a client. It's just not a big deal.

[...] So, your downlink
is virtually rain proof. The bad news is that the same cannot
be said about your uplink.

Hmmm...okay, I see. I wasn't aware that they didn't provide a high enough
power transmitter to deal with weather.

Solstices only knock communication off for several minutes a day,
when the Sun is directly behind the satellite. It is a well known
effect. I used to depend on an old Soviet satellite Raduga-7
for connectivity, and it was true back then.

Several minutes? I guess I'd call that insignificant. That's what, 10
minutes of downtime per year? Big deal. I have to deal with that kind of
downtime with my wired DSL access.

Pete

"Peter Duniho" wrote in message
...
"Pete Zaitcev" wrote in message
news
This depends on how big the data piece is relative to the
starting handshake. Consider that TCP start-up involves
so-called 3-way handshake, and that many protocols have
a setup phase when client and server exchange messages
strictly in simplex, before bulk data transmission can commence.

Regardless, that still only affects the initial delay in response.

The number of DNS queries to render any particular page can drive this time
up quite high. Have a couple packets lost in between? ouch.

$1000 a year is a bit steep for the class of service.

"Robert Henry" wrote in message
news:hpK0b.11202$uh6.8355@lakeread05...
The number of DNS queries to render any particular page can drive this
time
up quite high. Have a couple packets lost in between? ouch.

That's just silly. Especially for the typical use in an FBO, the number of
DNS queries to render any particular page is going to be quite small.
Furthermore, there's no need for DNS queries to be serviced sequentially,
and I doubt any browser would do it that way. I know that IE doesn't.

Once they get the initial page HTML, any additional Internet addresses that
need a DNS query to be resolved can and will be handled asynchronously. In
other words, a dozen DNS queries required by a single page isn't going to
take much more time than one additional DNS query would take.

$1000 a year is a bit steep for the class of service.

Only if you can have DSL or a cable modem installed. If you are in the
boonies and satellite is the fastest, most reliable Internet connection you
can get, $1000/year isn't that bad at all.

Pete

"Peter Duniho" wrote...
"Pete Zaitcev" wrote...
This depends on how big the data piece is relative to the
starting handshake. Consider that TCP start-up involves
so-called 3-way handshake, and that many protocols have
a setup phase when client and server exchange messages
strictly in simplex, before bulk data transmission can commence.

Regardless, that still only affects the initial delay in response. Even
if
the delay were 10 seconds (which it's almost never going to be), that's in
the same ballpark as the delay some servers have just getting around to
servicing a client. It's just not a big deal.

Ever tried VOIP over satellite? Painful, is a good one word discription,
same for remote access applications, network gaming as mentioned is
impossible...

[...] So, your downlink
is virtually rain proof. The bad news is that the same cannot
be said about your uplink.

Hmmm...okay, I see. I wasn't aware that they didn't provide a high enough
power transmitter to deal with weather.

Someone who lives in the desert might not experience as much rainfall that
occurs in other parts of the USofA or other countries in the beam... Hmmm
Las Vegas just got flooded, so better wording might be, "on a regular
basis"...

Solstices only knock communication off for several minutes a day,
when the Sun is directly behind the satellite. It is a well known
effect. I used to depend on an old Soviet satellite Raduga-7
for connectivity, and it was true back then.

Several minutes? I guess I'd call that insignificant. That's what, 10
minutes of downtime per year? Big deal. I have to deal with that kind of
downtime with my wired DSL access.

Nearly 10 minutes per day spread over several days, twice a year...
Guaranteed to screw up something important that needed to be done,
everytime...

Satellite data delivery has faults, just making you aware of it... I've been
there done that (our lawyers got the money from the class action lawsuit
against Hughes) and won't geaux back (2 cards still sits in the deactivated
computers since '98, dishes are still pointed at the satellites) to anything
with a ping time over 90 ms to the world... I actually endured the loss of
the satellite itself once, and the repointing a few times due to bird
migration (moving from one satellite to another, as the provider sees
fit)...