Article View: borland.public.cppbuilder.nativeapi
Article #4560Re: Win2000 DCOM and Service Control Manager on PC Startup
From: Remy Lebeau (TeamB)
Date: Mon, 09 Jan 2006 19:24
Date: Mon, 09 Jan 2006 19:24
20 lines
1917 bytes
1917 bytes
"Colin B Maharaj" <noreply@myhost.com> wrote in message news:43c28913$1@newsgroups.borland.com... > my Service A is launching Service B, but Service A must know > that DCOM is up since Service B is using DCOM. Why, exactly, does Service A need to know whether DCOM is running? If Service B is the one that is using DCOM, then Service B, not Service A, should be the one to check for that. All Service A should worry about is whether Service B starts or not. And, in fact, Service B does not even need to explicitally check for DCOM anyway. The OS will handle that automatically. If Service B makes a DCOM call that fails, Service B can report on that. If it is during Service B's initialization, then Service B can fail to start altogether, which Service A can then detect. Service B can even report that it is failing to start specifically because of a DCOM failure, and then Service A can use that error info as needed. Gambit
Technical Details
Message-ID:
<43c2b86e$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news4.google.com!news.glorb.com!newsfeed.hal-mli.net!feeder1.hal-mli.net!news-out.newsfeeds.com!propagator2-sterling.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mailReferences:
<43c28913$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10cc67,b5df1992ad8a76ae X-Google-Attributes: gid10cc67,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> Newsgroups: borland.public.cppbuilder.nativeapi References: <43c28913$1@newsgroups.borland.com> Subject: Re: Win2000 DCOM and Service Control Manager on PC Startup Date: Mon, 9 Jan 2006 11:24:34 -0800 Lines: 22 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 68.69.17.41 Message-ID: <43c2b86e$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1136834670 68.69.17.41 (9 Jan 2006 11:24:30 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news4.google.com!news.glorb.com!newsfeed.hal-mli.net!feeder1.hal-mli.net!news-out.newsfeeds.com!propagator2-sterling.newsfeeds.com!in.nntp.be!caladan.landsraad.net!newsgroups.borland.com!not-for-mail