[2946] in Release_Engineering

home help back first fref pref prev next nref lref last post

Palladium Query

daemon@ATHENA.MIT.EDU (epeisach@Athena.MIT.EDU)
Sun Nov 8 18:37:48 1992

From: epeisach@Athena.MIT.EDU
Date: Sun, 8 Nov 92 18:37:40 -0500
To: jdaly@Athena.MIT.EDU
Cc: rel-eng@Athena.MIT.EDU


As per usual please enclose $250 consulting on Palladium work....
(Other items I work for cheaply like ice cream)

>1.      What DCE services does palladium use?
>
>        Palladium relies upon the DCE environment as a whole.
Palladium was written in a layered approach so that any service could in
theory be replaced without affecting anything else. The services which
are currently in use include:
	threads (for the scheduler)
	rpc 
	name service

We used this feature to debug subsystems when DCE was not working so
well.

Note: As DCE is shipped, all libraryies will be required. For instance,
rpc relies on nameservice and threads.

>2.      Is it really required that palldium get these services from DCE?
>
>        (tenative yes)
See above

>3.      If not, what needs to be done to the build scripts to
>                "glue in" these services from another source?
>
>        (?)
I don't remember exactly, but various libraries would need to be
changed. (These are all documented somewhere). In particular the
mit.v2/if directories contain the "service dependent code". 

	Ezra

home help back first fref pref prev next nref lref last post