Ok, there are some strangeness in service application that uses ComServ unit as a DCOM server base. But may be it is possible to use such application? Can we say that there is no difference between "DCOM server NEAR service" and "DCOM server IN service"? Has "DCOM server NEAR service" any advantages vs. ordinary DCOM server ?

Below is a copy of table from page that compares simple exe and in-service DCOM applications. One column is added namely the "DCOM server NEAR service" column. Just compare it with other columns. It is obvious that there is only one feature that differs the "DCOM server NEAR service" from ordinary DCOM server application. It is the ability to start in local system context. Is it enough? I think it is not.

Feature	Ordinary DCOM server	DCOM server in a service	DCOM server NEAR service
Automatic start due to client request
Starting in given user context
Starting in local system context
Starting as interactive user
Access/launch rights configuration
Remote starting	(due to client request only)
Remote stopping
Pausing
Several independent parts in one application
Independent profile configuration of each part
Independent controlling of each part