Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!ll-xn!ames!amdahl!howard From: howard@amdahl.UUCP Newsgroups: comp.protocols.appletalk Subject: Re: Skeleton AppleTalk Programs? Message-ID: <7254@amdahl.amdahl.com> Date: Tue, 26-May-87 18:19:20 EDT Article-I.D.: amdahl.7254 Posted: Tue May 26 18:19:20 1987 Date-Received: Thu, 28-May-87 01:04:39 EDT References: <8705211446.AA08471@hera.CS.UCLA.EDU> <488@ucdavis.UUCP> Reply-To: howard@amdahl.UUCP (The Toolmaster) Distribution: na Organization: Amdahl Corp, Sunnyvale CA Lines: 27 Keywords: Appletalk, drivers, ATP, sockets, development Summary: Lots of questions Question for all the Appletalk experts in this group. What are you using for development? Is MPW the way to go or is there "a better way." Do you suggest Pascal over C? Is MacApp any help when it comes to Appletalking? Is it possible to write the bulk of a socket listener in a High level lang.? Or is assembly all there is? If you write a driver above ATP and use asynch calls, will the system definitely show your driver all the network events first? Have I got this right? Is there some way you can insure your driver will get time if a application is not calling systemTask; without a VBL proc. Here is a real simple one that I haven't found the complete answer for yet. How do you get you're driver installed in the System Heap so it isn't as transient as the application? Is it just a matter of setting the bit in ResEdit? Is there anything wrong with an Init loading the driver (into the system heap)? Well, as if that isn't enough, that's all for now. I would really appreciate some answers from the experts out there. Mail me with answers and requests to see the answers and if there are enough of both, I'll post 'em. Thanks. -- "Plan for the future because that's where you Howard C. Simonson are going to spend the rest of your life." {hplabs,ihnp4,nsc}!amdahl!howard - Mark Twain - [ The disclaimer for this message may be found in my next article ]