[permalink] [id link]
AppleTalk was released for the original Macintosh in 1985, and was the primary protocol used by Apple devices through the 1980s and 90s.
from
Wikipedia
Some Related Sentences
AppleTalk and was
AppleTalk support was also available in most networked printers ( especially laser printers ), some file servers and a number of routers.
Additionally, AppleTalk was designed from the start to allow use with any potential underlying physical link.
AppleTalk was so easy to use that ad-hoc networks tended to appear whenever multiple Macs were in the same room.
With its release, AppleTalk Personal Network was renamed LocalTalk.
AppleTalk was at that time the most used networking system in the world, with over three times the installations of any other vendor.
A significant re-design was released in 1989 as AppleTalk Phase II.
With the purchase of NeXT and subsequent development of Mac OS X, AppleTalk was strictly a legacy system.
Support was added to OS X in order to provide support for the large number of existing AppleTalk devices, notably laser printers and file shares, but alternate connection solutions common in this era, notably USB for printers, limited their demand.
AppleTalk support was finally removed from the MacOS in Mac OS X v10. 6 in 2009.
Unlike most of the early LAN systems, AppleTalk was not built using the archetypal Xerox XNS system.
One key differentiation for AppleTalk was it contained two protocols aimed at making the system completely self-configuring.
The AppleTalk address resolution protocol ( AARP ) allowed AppleTalk hosts to automatically generate their own network addresses, and the Name Binding Protocol ( NBP ) was a dynamic system for mapping network addresses to user-readable names.
An AppleTalk address was a 4-byte quantity.
Note that, because a name translated to an address, which included a socket number as well as a node number, a name in AppleTalk mapped directly to a service being provided by a machine, which was entirely separate from the name of the machine itself.
This was a comparatively late addition to the AppleTalk protocol suite, done when it became clear that a TCP-style reliable connection-oriented transport was needed.
ATP was the original reliable transport-level protocol for AppleTalk, built on top of DDP.
At the time it was being developed, a full, reliable connection-oriented protocol like TCP was considered to be too expensive to implement for most of the intended uses of AppleTalk.
NBP was a dynamic, distributed system for managing AppleTalk names.
This was the only part of AppleTalk that required periodic unsolicited broadcasts: every 10 seconds, each router had to send out a list of all the network numbers it knew about and how far away it thought they were.
ZIP was the protocol by which AppleTalk network numbers were associated with zone names.
AppleTalk and for
AppleTalk is a proprietary suite of networking protocols developed by Apple Inc. for their Mac computers.
AppleTalk included a number of features that allowed local area networks to be connected with no prior setup or the need for a centralized router or server of any sort.
A thriving 3rd party market for AppleTalk devices developed over the next few years.
PhoneNet allowed AppleTalk networks to be connected together using normal phone wires, even existing runs already being used for phones.
Apple had considered the problem, and AppleTalk included the possibility for a low-cost LocalTalk-to-Ethernet bridge, but they felt it would be a low-volume product and left it to 3rd parties.
These included updates to EtherTalk and TokenTalk, AppleTalk software and LocalTalk hardware for the IBM PC, EtherTalk for Apple's A / UX operating system allowing it to use LaserPrinters and other network resources, and the Mac X. 25 and MacX products.
However, the loss of AppleTalk did not reduce the desire for networking solutions that combined its ease-of-use with IP routing.
For socket numbers, a few well-known numbers were reserved for special purposes specific to the AppleTalk protocol itself.
When powered on, an AppleTalk machine broadcasts an AARP probe packet asking for a network address, intending to hear back from controllers such as routers.
The Apple Filing Protocol ( AFP ), formerly AppleTalk Filing Protocol, is the protocol for communicating with AppleShare file servers.
Built on top of AppleTalk Session Protocol ( for legacy AFP over DDP ) or the Data Stream Interface ( for AFP over TCP ), it provides services for authenticating users ( extensible to different authentication methods including two-way random-number exchange ) and for performing operations specific to the Macintosh HFS filesystem.
The initial default hardware implementation for AppleTalk was a high-speed serial protocol known as LocalTalk that used the Macintosh's built-in RS-422 ports at 230. 4 kbit / s.
AppleTalk and original
The Apple Filing Protocol ( AFP ), formerly AppleTalk Filing Protocol, is a proprietary network protocol that offers file services for Mac OS X and original Mac OS.
AppleTalk and Macintosh
At the time, Apple planned to release a suite of AppleTalk products as part of the Macintosh Office, with the LaserWriter being only the first component.
Many of the built-in Macintosh peripherals can be " borrowed " by the card when in Apple II mode ( i. e. extra RAM, 3 floppy, AppleTalk networking, clock, hard disk ).
The first popular videogaming title to release a LAN version was Spectre in 1991 for the Apple Macintosh, featuring AppleTalk support for up to eight game players.
One example was the support of AppleTalk on Macintosh computers during the brief period in which Apple Computer supported the Open Transport networking system.
Windows NT Server ( 3 and 4 ) only supported AppleTalk, 2000 added AppleShare over IP ; Services for Macintosh ( SFM ), was removed from Windows Server 2008 onwards.
AppleTalk and 1985
When the newly-christened AppleTalk shipped in early 1985, it included a number of compromises.
AppleTalk and protocol
* AppleTalk Session Protocol, a session layer protocol used by the AppleTalk suite of protocols
The rise of TCP / IP during the 1990s led to a re-implementation of most of these types of support on that protocol, and AppleTalk became unsupported as of the release of Mac OS X v10. 6 in 2009.
The AppleTalk design rigorously followed the OSI model of protocol layering.
Each node dynamically chose its own node number, according to a protocol ( originally the LocalTalk Link Access Protocol LLAP and later the AppleTalk Address Resolution Protocol, AARP ) which handled contention between different nodes accidentally choosing the same number.
AEP ( AppleTalk Echo Protocol ) is a transport layer protocol designed to test the reachability of network nodes.
* Kinetics Internet Protocol ( KIP ), an AppleTalk network protocol
Although this market segment is now much reduced, the technologies developed in this area continue to be influential on the Internet and in both Linux and Apple Mac OS X networking — and the TCP / IP protocol has now almost completely replaced IPX, AppleTalk, NBF, and other protocols used by the early PC LANs.
Based on the AppleTalk protocol stack, LocalTalk connected the LaserWriter to the Mac over an RS-422 serial port.
Other examples of session layer implementations include Zone Information Protocol ( ZIP ) – the AppleTalk protocol that coordinates the name binding process, and Session Control Protocol ( SCP ) – the DECnet Phase IV session-layer protocol.
The IIGS also supported booting from an AppleShare server, via the AppleTalk protocol, over LocalTalk cabling.
Network Control Protocols include the Internet Protocol Control Protocol for the Internet Protocol, the Internetwork Packet Exchange Control Protocol for the Internet Packet Exchange protocol, and the AppleTalk Control Protocol for AppleTalk.
Thousands of Mac programs were based on the AppleTalk protocol ; in order to support these programs, AppleTalk was re-implemented as an OpenTransport " stack ", and then re-implemented as an API shim on top of this new library.
0.118 seconds.