Path: news1.ucsd.edu!ihnp4.ucsd.edu!agate!howland.reston.ans.net!math.ohio-state.edu!uwm.edu!lll-winken.llnl.gov!apple.com!seeding.apple.com!user From: garryh@seeding.apple.com (Garry Hornbuckle) Newsgroups: comp.sys.mac.comm Subject: Open Transport FAQ part 2 - Technologies Date: Tue, 31 Oct 1995 08:44:18 -0800 Organization: Apple Computer, Inc. Lines: 192 Message-ID: <garryh-3110950844180001@seeding.apple.com> NNTP-Posting-Host: seeding.apple.com Apple Open Transport Frequently Asked Questions Part Two - Component Technologies Extracted from: Open Transport Background Q & A Version 1.8 (OT 1.0.8 Release) October 19, 1995 Component Technologies Q: What technology components comprise Open Transport? A: Open Transport supports LANs and WANs and will integrate serial communications, modems, and remote (dial-up) networking in a consistent model for end-users, network managers, and developers. The Open Transport architecture consists of: * standards-based programming interfaces for applications developers and for network interface controller developers, * a new cross-platform development model for integration of networking with the underlying operating system, * new implementations of MacOS protocol stacks, * new human interface applications and control panels, and * a set of backward-compatibility support modules. Q: What standards are implemented in the Open Transport architecture? A: Open Transport brings standards-based networking into the MacOS with support for: * the X/Open Transport Interface (XTI), the POSIX compliant API for support of networking applications, * a port of a UNIX System V release 4.2 compatible STREAMs environment for network protocol developers, and * the Datalink Provider Interface (DLPI), for development of network interface controller (NIC) drivers. Q: Did Apple develop the STREAMs environment for Open Transport? A: To maximize the stability, performance, and robustness of Open Transport, Apple selected Mentat Inc. - the leading supplier of high performance kernel-level network software - to supply both the STREAMs environment and the code base for Open Transport/TCP. Mentat Portable STREAMs (MPS) is an independent fast, full-featured, multiprocessor safe version of the UNIX System V Release 4 STREAMs environment. Its inclusion in Open Transport provides a reliable platform for Open Transport protocols, including Apple's own implementation of a STREAMs-based AppleTalk stack. MPS also allows easy porting from other platforms of third party protocols. MPS is the same implementation of STREAMs found inside many UNIX operating systems including those from IBM and OSF, as well as other platforms such as Novell NetWare. Mentat TCP (MTCP) is a robust implementation of TCP/IP that conforms with all industry standards, and makes a significant contribution to the performance and functionality of Open Transport/TCP. Q: Is there more information available about Mentat Inc. and its products? A: Mentat maintains a presence on the world wide web at: http://www.mentat.com Q: Which protocols are supported by Open Transport? A: Open Transport version 1.0.x includes new, native implementations of AppleTalk, and TCP/IP, and new consistent API access to serial communications. Apple and third parties are working to add support to Open Transport for Point to Point Protocol (PPP), NetWare (NCP/IPX), Windows 95 (SMB/TCP/NetBIOS), DECnet, LAT, and X.25. Some of these additional capabilities may be incorporated or bundled with future releases of Apple Open Transport (see Future Directions). Q: What current MacOS technologies, components, and products will Open Transport replace? A: When installed Open Transport replaces the current MacOS implementations of AppleTalk and TCP/IP (including the protocols and the "Network", "MacTCP", and "Admin TCP" control panels). Open Transport is also designed to replace the Connection Manager and the Communications Resource Manger of the current Communications Toolbox architecture. Sometime after Open Transport ships as a shrink-wrap software package for the installed base of Macintosh systems, it is planned to replace the "AppleTalk Connection for Macintosh" and "TCP/IP Connection for Macintosh" products. Q: Is Apple is migrating serial communications away from the Communications Toolbox (CTB)? A: Partially, but not entirely. The CTB File Transfer and Terminal Managers continue to be supported and will be preserved in the Copland OS release - although on new Open Transport/Serial underpinnings. Over time, plans call for the CTB Connection Manager and its tools to be phased out in favor of Open Transport. In particular, while the Copland release of the MacOS is expected to provide support for the Connection Manager APIs, at this time Apple has no plans to port the existing Connection Tools to Copland. Thus, Apple recommends that developers plan their update to Open Transport/Serial (and away from CTB Connection Manager) to coincide with (or precede) the availability of the Copland OS release. Q: What key files are present when Open Transport has been installed on a MacOS system? A: When installed, Open Transport adds the following Extensions to the MacOS System Folder: * Open Transport Library Open Transport code resource for 680x0-based Macintosh systems. * Open Tpt AppleTalk Library Code resource for AppleTalk communication protocol for 680x0-based Macintosh systems. * Open Tpt Internet Library Code resource for TCP/IP communication protocol for 680x0-based Macintosh systems. * OpenTransportLib Open Transport code resource for PowerPC-based Macintosh systems. * OpenTptAppleTalkLib Code resource for AppleTalk communication protocol for PowerPC-based Macintosh systems. * OpenTptInternetLib Code resource for TCP/IP communication protocol for PowerPC-based Macintosh systems. * Ethernet (Built-In) Code resource to allow access to built-in Ethernet port. * Serial (Built-In) Code resource to allow access to built-in serial port. Q: Are there any changes in AppleTalk or TCP/IP with Open Transport? A: Yes. The new Open Transport/AppleTalk and Open Transport/TCP protocol stacks both have been implemented as Open Transport STREAMs modules and as native code on Power Macintosh computers. They support the new XTI APIs, and their shared libraries can be dynamically loaded and unloaded as needed. Both protocols also support dynamic reconfiguration (changed settings without requiring reboot), and feature new configuration applications offering Basic, Advanced, and Administrator tools. The new configuration applications - AppleTalk and TCP/IP - replace the older control panel implementations - Network, MacTCP, and AdminTCP. For backward compatibility purposes, the new applications continue to be stored in the Control Panels folder in the System Folder. Each protocol stack also offers addition protocol-specific feature enhancements. Network Interface Options Q: What network interface options are available with Open Transport? A: Open Transport v1.0 supports PCI-bus NICs and Macintosh built-in (LocalTalk and ethernet) network adapters. Beginning with v1.0.6, Open Transport adds support for infrared and PC Card (formerly known as PCMCIA) network adapters on select Macintosh systems. Third party options available for Open Transport include fast ethernet, ATM, and FDDI. Q: What about dial-up network connectivity solutions? A: For connectivity to AppleTalk networks, Open Transport supports Apple Remote Access v2.0.1 client and personal server through backward compatibility services. For dial-up connectivity to TCP/IP networks including the Internet, Open Transport supports select third party MacTCP software extensions (known as mdevs), providing SLIP or PPP connectivity. See Network Compatibility for more information. Open Transport and Cross-Platform Issues Q: Will Apple port Open Transport to Windows or UNIX? A: Apple does not plan to port Open Transport to other operating systems. Rather, Open Transport is based on Apple porting three existing, cross-platform industry standards to the MacOS. These standards have their roots in the UNIX community and experienced UNIX network developers will find themselves "right at home" when developing for Open Transport. Q: What about Windows developers? What about Windows Sockets? A: NetManage, the leading developer of TCP/IP protocols and applications for DOS and Windows, has announced plans to develop and offer Windows Socket tools for MacOS, to provide access to Open Transport/TCP and MacTCP services via the Windows Sockets (Winsock 1.1) API. Additional details of this announcement will be made public at a later date. Q: With both XTI and Windows Sockets available for Open Transport, which API should a developer use? A: The choice of API will depend upon a developer's background, experience, and goals. For developers with a background in UNIX, a need for POSIX compliance, or a need to deploy an application across MacOS and UNIX systems, XTI is the logical choice. For developers with a background on Microsoft Windows, or a need to deploy an application across MacOS and Windows, Windows 95, and/or Windows 95 systems, the planned Winsock tools from NetManage will provide an attractive cross-platform alternative. Apple is committed to XTI and will focus development on transport independence around this API. Macintosh developers now using classic AppleTalk or MacTCP APIs are encouraged to move to Open Transport XTI API. ------------------------------------------------------------------- Garry Hornbuckle Product Manager, Communications & Collaboration ------------------------------------------------------------------- "If I told you that I | email garryh@seeding.apple.com spoke only for myself | applelink HORNBUCKLE1 would you believe me?" | fax (408) 974-1211 -------------------------------------------------------------------