han@Apple.COM (Byron "No Comments" Han) (06/26/89)
In article <7764@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >I have some questions about the Communications Toolbox -- > >(1) What is the connection between statements about licensing and >statements that this will become a standard part of the OS with System >7.0? Do all products using it have to license it (if they provide a >copy) or will it be subsumed under distributing the Apple system >software for licensing purposes? > Well, in order to distribute Apple software with your commercial products, typically developers pay a license fee to Apple for the right to include Apple software with commercial products. I am no expert on these matters - you should contact Apple SW Licensing for more information. >(2) The distributed diagrams show only serial port support built in. >I am surprised that support for network terminals (using TCP and ADSP) >and network file transfer (using FTP and perhaps client-side AFP) >weren't slated for the first release. Will these be added later or is >this being left for third parties? If only serial connections modules >are being provided, how sure can we be that it is general enough for >LAN use? > I guess I could put on my Joe Isuzu hat and say "Trust Me". :-) Actually, we have prototyped many different connection tools support different connection protocols. But there has been a conscious decision to NOT provide each and every different connection tool supporting all different connection protocols. We have prototyped ADSP, TELNET, and 3270 connections so the architecture DOES support these different connection methods. Also, DEC's LAT protocol will be supported via a connection tool. And the MacX.25 MacPAD will be implemented as a connection tool. >(3) Will it be compatible with System 6.0.3 as well as 7.0? > The Communications Toolbox will be compatible with System 6.0.x and 7.0. It will be fully 32-bit clean and virtual memory compatible. It will run on machines with 1 megabyte of RAM. Single floppy _is_ possible although stretching it a bit. >(4) What responsibilities of terminal emulation are left to the >application (or other calling) software? For instance, do the built-in >terminal emulators implement scrollback and connection-time saving to >disk, or are there callback hooks to allow client software to handle >these features? > Caching of data that scrolls off the "top" of the terminal screen is performed via a callback procedure. The terminal tool, when it is about to "lose" a line off the top of the terminal, will call this callback procedure (if one is specified) >Thanks for any help you can give.... Hope this helps. > be considered patriots. This is one nation under God." > -- George Bush in FREE INQUIRY magazine, Fall 1988 +-----------------------------------------------------------------------------+ | Disclaimer: Apple has no connection with my postings. | +-----------------------------------------------------------------------------+ Byron Han, Communications Scapegoat At Apple, we change the world everyday. Apple Computer, Inc. ----------------------------------------- 20525 Mariani Ave, MS27Y Internet: han@apple.COM Cupertino, CA 95014 UUCP:{sun,voder,nsc,decwrl}!apple!han ------------------------------------ GENIE:BYRONHAN CompuServe:72167,1664 ATTnet: 408-974-6450 Applelink:HAN1 HAN1@applelink.apple.COM -------------------------------------------------------------------------------