[265] in Info-AFS_Redistribution
Re: ka_*() API specifications
daemon@ATHENA.MIT.EDU (Craig_Everhart@transarc.com)
Fri Aug 2 13:31:33 1991
Date: Fri, 2 Aug 1991 12:45:03 -0400 (EDT)
From: Craig_Everhart@transarc.com
To: Info-AFS@transarc.com, Cal_Thixton@next.com
In-Reply-To: <9108020433.AA14066@dorothy.NeXT.COM>
This isn't a Transarc-official statement, but I thought I could point at
something helpful.
The Andrew software does at least some of what you want, packaging
authentication information in one process and passing it to another.
(Andrew is available as part of X.V11R4, and a far more recent version
is available either by anonymous FTP from emsworth.andrew.cmu.edu or by
sending mail to the automatic daemon andrew-service@andrew.cmu.edu .)
The relevant functions are in {andrew}/overhead/util/lib, in the
tokpak.c and tokunpak.c modules. Example uses of these functions would
be found in {andrew}/overhead/mail/lib/dropoff.c, where the user's
authentication is packaged for transmission to the local queuemail
daemon, and {andrew}/ams/delivery/queuem/queuem.c, where the package
containing the user's authentication is opened and borrowed.
AMDS mail enqueueing uses these functions because mail is enqueued in
the user's ~/.Outgoing directory, and then a packet bearing
authentication and other information is shot to the local queuemail
daemon, which uses the authentication and carries out the mail delivery.
It sounds like your prospective uses (background printing and such) are
comparable.
Craig
