🚀 go-pugleaf

"david johnson" <davidjohnson@gmail.com> wrote in message
news:43dbb7d8@newsgroups.borland.com...

> When a run a client, it instanciates the server and the server is loaded
> up on the "server" machine.  What I want to know is, what happens if
> no one is logged on to the windows machine i.e. it is just sitting at the
> login screen.

That depends - is the DCOM server implemented in a standalone application,
or as an actual service?

> Will the server app still start?  If so, what then happens when someone
> logons on - will they see the server GUI on there desktop?

If you implement the server as a true service, then everything will work
fine as expected - the server can be started even if no user is logged in,
and the service will continue to run when a user does eventually log in.

> I'm not sure what sure what the results are...

Did you actually try it as see what really happens?

> I need to server to run regardless of if a user is logged on to the server
PC

Then you must implement the server as a service.

> Is it possible to wrap DCOM into an NT service?

Yes.  Microsoft even provides extra support in the OS for that specific
condition, in the form of additional Registry values that you need to set up
during the service's installation.  Read the following article for more
details:

    Creating and Registering COM Components with LocalService
    http://msdn.microsoft.com/library/en-us/dncomg/html/localserv.asp


Gambit