[284] in Athena_Backup_System
Re: crippled mode server issue
daemon@ATHENA.MIT.EDU (delgado@MIT.EDU)
Tue Jul 2 15:59:07 1996
From: delgado@MIT.EDU
To: Bill Cattey <wdc@MIT.EDU>
Cc: athena-backup@MIT.EDU, delgado@MIT.EDU
In-Reply-To: Your message of "Tue, 02 Jul 1996 13:21:21 EDT."
<glqJeFgGgE6e01NWo0@mit.edu>
Date: Tue, 02 Jul 1996 15:59:00 EDT
>Am I learning from this that ONC RPC is "not a real rpc" because there
>is no way to register an internal routine to operate periodically from
>inside the svc_run loop?
No, ONC RPC is a real RPC. This is just a characteristic of programs
which use this paradigm. For the most part, with client/server the
server is not ever interactive, and it primary role is to execute
requests from clients (in a non-interactive fashion). So this restriction
actually makes sense. We just have an out of the ordinary requirement
for the crippled mode.
It would not be difficult or even ugly to export a second interface,
similar to what we currently do for the real Master (we have two
separate interfaces one for ui, one for slaves) to which the
crippled mode ui can direct its requests. Much of the info can
be prompted for and sent over in one call. The RPC does has the ability
to listen for requests on multiple interfaces; you just
create and register a second interface with the RPC before calling
svc_run. (Look at master_main.c for an example).
