Xref: utzoo comp.protocols.appletalk:2251 comp.sys.mac:35089
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!apple.com!falken
From: falken@apple.com (Dave Falkenburg)
Newsgroups: comp.protocols.appletalk,comp.sys.mac
Subject: Re: MultiLaunch programs on Apple Share
Message-ID: <2828@internal.Apple.COM>
Date: 14 Jul 89 01:19:54 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 21
References:<278@surf.sics.bu.oz> <3877*kenw@noah.arc.cdn> <1268@intercon.UUCP>

In article <1268@intercon.UUCP> kdb@intercon.uu.net (Kurt Baumann) writes:
> What methods have you thought of?  I would be curious, perhaps you could
> help us to do a better job.

there are a few methods that i can think of right away:

1) have the server monitor keep a ref count for opening up the resource
   fork of a file (since AFP is statefull, unlike nfs, this wouldn't be
   impossible) Basically, AppleShare could work this alot like the "copy
   protection" in AppleShare 2.0

2) devise a license validation/ check-in / check-out protocol that can be
   implemented by vendors.  This would require a great deal of cooperation.

-dave
 falkenburg

disclaimer:  i don't work for networking & communications,
             i'm in system software

#include <disclaimer.h>