[280] in Athena_Backup_System
crippled mode server issue
daemon@ATHENA.MIT.EDU (delgado@MIT.EDU)
Fri Jun 28 08:59:47 1996
From: delgado@MIT.EDU
To: athena-backup@MIT.EDU
Date: Fri, 28 Jun 1996 08:59:43 EDT
Here's something obvious that I overlooked while reading the
crippled mode design spec.
The way I understand crippled mode is that the interactive ui and
fake master are one process, correct?
From the spec, I am not clear on how crippled mode master provides an
interactive UI while it is also listening for incoming ABS_SLAVSERVICE
requests via the RPC.
Typically, and RPC server is implemented as follows:
1. perform process initializations
2. perform RPC initializations (register interfaces, etc).
3. Call svc_run()
"svc_run" is an rpc library call which under normal
circumstances never returns. Its function is to
listen for incoming network requests and execute
the requested interface call.
This model does not naturally lend itself to being interactive.
I think we need to specify in more detail how this is going to
be implemented.
