Re: user defined WM_ question: update

Stoyan Damov <[email protected]>
Newsgroups gmane.comp.windows.off-topic
Message-ID <[email protected]>
You *can't* possibly be thinking that every Windows machine
continuously polls all machines on the network to detect if any of
them is down.
If that's what you're trying to accomplish, develop an app which
multicasts heartbeats on a configurable time interval and run it on
all machines. Then, on the machine on which you'd like to detect
outages, create and run an app which listens for such heartbeats,
collects all ips from the heartbeats, and if it detects that an ip
hadn't sent a heartbeat in some time interval it notifies the UI.

Anything "simpler" sounds like "I need a Delphi component which can
put a lion in a cage which I can drop on my form"...

Cheers

On Wed, Aug 26, 2009 at 12:41 AM, Eric Strain<eric_strain1-/[email protected]> wrote:
>
>
> Hi Curt,
>   Thanks for the reply. What I am trying to do is have my application
> automatically know as soon as any network failure of any kind occurs. This
> includes anything from someone unplugging the network cable, to a server on
> the network going down for some reason. I'm using MFC with VC6.0
> Professional IDE on WinXP. I'm hoping there is an API available and that I
> don't have to resort to .NET to accomplish what I want. Any ideas?
>
> -Eric
>
> --- On Mon, 8/24/09, Curt Hagenlocher <[email protected]> wrote:
>
> From: Curt Hagenlocher <[email protected]>
> Subject: Re: [OT] user defined WM_ question: update
> To: [email protected]
> Date: Monday, August 24, 2009, 4:24 PM
>
>
>
> I imagine you still need some kind of listener for the "targeted event".
> Your listener could then use PostMessage(WM_MYEVENT, 0, 0) to tell the UI
> thread that the event has happened. You haven't provided any specific
> information about the "targeted event", though -- for all I know, it's got a
> specialized API to do exactly what you want.
> On Mon, Aug 24, 2009 at 2:00 PM, Eric Strain <eric_strain1-/[email protected]> wrote:
>>
>>
>> OK, I got the WM_USER code to work, now is it possible to get the event
>> handler to fire automatically? I really don't want to use polling, even if
>> it is on a separate thread. Currently I have the WM_USER event being
>> triggered through SendMessage(WM_MYEVENT,0,0); inside an OnClicked( )
>> handler attached to a UI button. Although this is working in my test app, I
>> want the event to be fired automatically by the OS when the targeted event
>> occurs.
>>
>> Any ideas? Thanks guys.
>>
>> -Eric
>>
>> --- On Sun, 8/23/09, Eric Strain <eric_strain1-/[email protected]> wrote:
>>
>> From: Eric Strain <eric_strain1-/[email protected]>
>> Subject: [OT] user defined WM_ question
>> To: [email protected]
>> Date: Sunday, August 23, 2009, 5:17 PM
>>
>>
>>
>> Hi All,
>> I have a function that I need to fire when a specific event occurs. The
>> event that I need to trap is a network failure of any kind. I have the code
>> that detects when a network failure has occurred but at present the function
>> is inside a command line interface program and I want to transfer that
>> function into an MFC app and have the function activated by a WM_ event. My
>> question is, is it possible to get the user defined WM_ to fire
>> automatically, or does the user have to send the event message manually,
>> such as by clicking a UI button or something?
>>
>> Also, I considered using WM_USER to define the custom WM_ message, but my
>> research indicates that WM_APP is the preferred method for defining a custom
>> message. Any thoughts on this? Even better, any concrete examples? ; ) I've
>> looked all over the net and through my library of books with no luck. It's a
>> shame a person can't loose weight by running in circles, because I seem to
>> be getting nowhere fast. Thanks guys.
>>
>> -Eric
>>
>>
>>
>>
>>
>>
>
>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.