Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!helios.ee.lbl.gov!ux3.lbl.gov!milburn
From: milburn@ux3.lbl.gov (John Milburn)
Newsgroups: comp.protocols.appletalk
Subject: Re: LaserShare 2.0
Message-ID: <1934@helios.ee.lbl.gov>
Date: 16 Feb 89 07:47:36 GMT
References: <15283@oberon.USC.EDU>
Sender: usenet@helios.ee.lbl.gov
Reply-To: JEMilburn@lbl.gov (John Milburn)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 16

AppleShare Print Server 2.0 does have one major problem. AppleShare 2.0
allows for concurrent applications as well as background applications.
An example of a (reasonably) well behaved background application is
CE's QuickMail MailCenter server. It sits there in the background and just
works. AppleShare Print Server 2.0, on the other hand, is a concurrent
application, which means that while it is running you will have to access to
administer your file server or mailcenter. The ability to administer the
file server while online was the major feature enhancement of AppleShare 2.0,
and the print spooler designed (**rather patched**)to work with it
effectively circumvents this capability.

Other than this and the problems with long PostScript records, it does work
quite well. Mine is spooling to two LaserWriters from fifty macs.

John Milburn - Advanced Light Source - Lawrence Berkeley Laboratory
JEMilburn@lbl.gov