Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!astroatc!nicmad!madnix!jason
From: jason@madnix.UUCP (Jason Blochowiak)
Newsgroups: comp.sys.apple
Subject: Re: communicating via appletalk
Keywords: appletalk, bulletin boards, communications
Message-ID: <1129@madnix.UUCP>
Date: 19 Feb 90 14:48:35 GMT
References: <22323@unix.cis.pitt.edu> <1122@madnix.UUCP>
Reply-To: jason@madnix.UUCP (Jason Blochowiak)
Organization: ARP Software, Madison, WI
Lines: 25


	I forgot one relatively simple solution: Seeing as the fileserver
software already exists (and I presume it works), why not use it? So, instead
of using the Mac to run the BBS program, have each Apple // running some
software that deals with a set of files on the Mac's hard drive. Of course,
you'll have to deal with the problems normally associated with concurrency,
but I doubt that you'll need anything really high performance, so you could
take a fairly simple way out. Something like this could be written in
AppleSoft Basic by a fairly competent high-schooler, it'd be cheap (assuming
you already have the AppleTalk network set up, with the Mac running as a
file server), and it should provide an adequate solution.

	Re-reading that 'graph, I see that it's not the clearest in terms of
the solution I'm suggesting. I can't figure out how to properly re-write it,
so here's another attempt: Each Apple // would be running the BBS program.
All of the files associated with the BBS would be held on the Mac, which would
be running as an AppleShare fileserver. Each copy of the BBS program would
act according to a strict set of rules regarding file access, so that integrity
could be maintained. Each copy of the BBS would be able to read the posts,
and allow the student logged in to post as well - the complexity and
sophistication would be up to you.
-- 
                      Jason Blochowiak - jason@madnix.UUCP
or, try:         astroatc!nicmad!madnix!jason@spool.cs.wisc.edu
       "Education, like neurosis, begins at home." - Milton R. Saperstein