Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!ucsd!rutgers!cbmvax!dale From: dale@cbmvax.commodore.com (Dale Luck - Amiga) Newsgroups: comp.sys.amiga.tech Subject: Re: Architecting a remote dungeon Keywords: Dungeon Platform Message-ID: <12491@cbmvax.commodore.com> Date: 9 Jun 90 03:37:53 GMT References: <136840@sun.Eng.Sun.COM> <12411@cbmvax.commodore.com> <136932@sun.Eng.Sun.COM> Reply-To: dale@cbmvax (Dale Luck - Amiga) Organization: Commodore, West Chester, PA Lines: 28 In article <136932@sun.Eng.Sun.COM> cmcmanis@stpeter.Eng.Sun.COM (Chuck McManis) writes: >In article <12411@cbmvax.commodore.com> jesup@cbmvax (Randell Jesup) writes: >> ... Go to Dale's talk at Devcon, if you're going to be >>there. (SANA = Standard Amiga Network Architecture, which the Amiga >>Network working group run by Dale has standardized on.) ... > >I'm a little bit confused about this. Since Commodore is using SVR4 >for the base of it's AMIX product, why not use the TLI interface >which is standard in SVR4 to help developers maintain applications >that work both under AmigaDOS and UNIX ? > The TLI stuff is only a shell over one of the SANA layers. It is just similar to BSD sockets or whatever libraries are used to write Mac network applications or DEC VMS applications. The stuff that sits underneath the interface library is based on exec devices and ioreqs. This will mean than tli based programs as well as bsd socket applications can coexist in the same box since the underlieing interface is common and reentrant, just like all good devices. I am looking for a volunteer to develop a TLI library along with the socket library I already have to see if we are missing some critical functions that are necessary to support TLI properly. Having a TLI based application you want to port to the Amiga is probably a good start. Dale Luck Commodore-Amiga, Inc.