Re: Running scripts over network
Re: Running scripts over network
- Subject: Re: Running scripts over network
- From: Bill Briggs <email@hidden>
- Date: Sat, 17 Aug 2002 15:37:25 -0300
At 1:57 PM -0400 17/08/02, Dave DeLong wrote:
Non-TCP/IP networks (such as AppleTalk) are way cool because you
don't have to screw around with the whole IP address thing and stuff.
And they are way limited because you can't reach past your local
LAN/WAN that supports AppleTalk.
I frequently attend my local MUG where they are forever trying to
access the internet on the TCP/IP network in the building, but can
NEVER do it.
This sounds silly. The internet runs on IP protocols (TCP, UDP,
etc.). If they can't access the internet then they don't know how to
set up a Mac for the internet (drop dead easy), or they are kept off
by a firewall that has all the relevant ports blocked.
So, based on my experiances, TCP/IP is just a really complicated way
of networking that doesn't seem to work too well.
On the contrary, it works brilliantly. The entire net runs on it.
Given the scale of the infrastructure and the level of usage, it's
nothing short of remarkable that it all works so well.
AppleTalk, on the other hand, has never given me any problems at all
and is very stable. So, AppleTalk is way cool.
AppleTalk is only good for you to talk to other Macs (or PCMacLan
equipped PCs) on your network. Stability isn't an issue. Connectivity
is.
From an earlier post in this thread you seem to have the kind of
network hardware you are using, or the physical layer of the network
- twisted pair with 10 Base-T ethernet in your case - confused with
the communication protocols that this physical layer carries.
The kind of connection (in your case ethernet) in the physical layer
only indicate the hardware, the electrical signal levels, detection
thresholds, distance limits due to attenuation, and all of the other
basic electrical concerns to allow something to be transmitted and
received successfully at the other end. This is "electrical networks"
stuff as opposed to "computer networks" stuff that rides on it.
The higher layers - the "computer networks" stuff - are concerned
with how the information is "packaged", the error checking,
encryption (if any) packet ordering, connection setup and tear down
(where relevant), routing, packet reassembly, etc. A host of
activities that occurr out of sight to the user.
The main point to take away is that the physical connection -
ethernet, wireless, whatever - has nothing to do with the protocols
that are carried on it. Networks carry data using multiple protocols,
whether you are aware of it or not. To say that AppleTalk is way cool
and TCP/IP is flaky is to simply misunderstand nearly everything
about the network we are all using.
- web
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.