On Tue, Sep 29, 1998 at 09:11:44AM -0500, David Corcoran wrote:
> Please answer if you know the following question I'm going to ask. I'm looking
I don't know THE answer. This are only my opinions.
> now for the best way to make our current resource manager available to
> applications. What is the best way ? If the Resource Manager was a shared
> object with some variables declared statically would multiple apps be able to
> load and then communicate with the object simultaneously ? Or do I need to
No. Because each apps is a different process. You must use shared
memory to obtain what you expect from statically declared object.
> interface with the kernel somehow by making the resource manager attached to a
I don't like this option. I think it's difficult and dangerous, again I am
not sure it's needed.
> device. Or maybe we could make it a daemon upon startup but then you have to
> deal with interprocess communications.
I prefer this choice. At least because the daemon does not need to run as
root and can't crash my PC (I hate rebooting :).
--
Ciao Walter.
C makes it easy for you to shoot yourself in the foot. C++ makes that
harder, but when you do, it blows away your whole leg.
-- Bjarne Stroustrup
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
