To the main page...The list of my products...Some texts...Sample applications, tips, tricks...If you need support...

DCOM server in Windows NT Service
Comparison of "NEAR" and "IN" servers

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 yes yes yes
Starting in given user context yes yes yes
Starting in local system context no yes yes
Starting as interactive user yes no no
Access/launch rights configuration yes yes yes
Remote starting yes (due to client request only) yes yes
Remote stopping no yes no
Pausing no yes no
Several independent parts in one application no yes no
Independent profile configuration of each part no no no
Independent controlling of each part no yes no
<< | Index | 1 | 2 | 3 | 4 | 5 | >>

© 1998-2001 Alexey Dynnikov
My ICQ # is 18267212