Re: Client may not start server twice
From: Alexander Nickolov (agnickolov_at_mvps.org)
Date: 11/09/04
- Previous message: Jeffery Kohler: "Using COM for interprocess communication?"
- In reply to: Peter: "COM : Client may not start server twice"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 9 Nov 2004 09:53:46 -0800
For the first question - use REGCLS_SINGLEUSE when you
register your class objects - COM will start a fresh server
process for each new client. Only works for out-of-proc
servers of course. REGCLS_MULTIPLEUSE does the opposite -
a single process serves all clients.
For the latter - modify the registration code of your out-of-proc
server not to register the LocalServer32 value. Then COM won't
be able to start your server, but clients can still conect to it when
it's running and its class objects are registered. Note you should
use REGCLS_MUTLIPLEUSE in that case - to allow multiple
client connections.
-- ===================================== Alexander Nickolov Microsoft MVP [VC], MCSD email: agnickolov@mvps.org MVP VC FAQ: http://www.mvps.org/vcfaq ===================================== "Peter" <Peter@discussions.microsoft.com> wrote in message news:D74813E0-49CA-42FE-B44E-B2DE91FEA173@microsoft.com... > Hello, > > I am running a server client application on a W2k PC or at two PCs. > > Does someone know how to configure a server that it can be started only > once > by a client ?? Or that a client can start a new server instance with each > call. > > Or how to configure a server that the client can connect to a server > interface only if the server is already running and that the client has no > permission to start the server at all?? > > Thank's for any tip > > Peter
- Previous message: Jeffery Kohler: "Using COM for interprocess communication?"
- In reply to: Peter: "COM : Client may not start server twice"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
