The Driver Interface: /lib/driver

The driver object is not really used explicitly by the simulation, except to checkpoint, shutdown the server, and manage network connections. DGD itself calls several functions in the driver object when certain events occur and other conditions arise.

The following functions are defined by the driver object:

notify()

write debugging output to stderr (also used as a proxy-connection)

checkpoint()

write a binary state dump

do_shutdown()

bring down the server

initialize()

called by DGD once at startup (bootstrap mode)

restored()

called by DGD once after a state restore

query_net()

return true iff DGD networking is installed and enabled

query_backdoor()

return true iff the wizard backdoor is enabled

path_ed_read()

called by DGD to translate an editor read path

path_ed_write()

called by DGD to translate an editor write path

path_object()

called by DGD to translate an object path

path_inherit()

called by DGD to translate an inherit path

path_include()

called by DGD to translate an include path

compile_object()

called by DGD to return a virtual object (calls GLOBAL->fetch_object())

recompile()

called by DGD to recompile an out-of-date object

telnet_connect()

called by DGD when a telnet connection is established

binary_connect()

called by DGD when a binary connection is established

compile_log()

called by DGD to return the name of a compile-time error log

log_error()

called by DGD to log a run-time error

rob@ccs.neu.edu