[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Heartbeat stopped messages
- Subject: Re: Heartbeat stopped messages
- From: patrick@xxxxxxxxxxxx
- Date: Tue, 15 Jun 2004 07:29:50 -0000
--- In xAP_developer@xxxxxxx, mcs101main@a... wrote:
> I agree with the alive/stopped heartbeat.
>
> Sometime in the future I propose that values other than black &
> white be available in support of a generalized health managment
> approach. For example, built-in-test infomation such as the
> connection to the RR was pulled from the PC but the RR connector is
> still running.
The original purpose of the heartbeat was simply to provide a
mechanism through which the hub was able to co-ordinate connections.
It's also useful, of course, in enabling discovery of active
applications on the network and it also provides a potential
mechanism for failover between apps.
I think notification of generic errors of this type should probably
use a standard class as a matter of policy (e.g. xap-user-error, xap-
technical-error) and intercepted and displayed in A.N.other GUI --
just because there's so many potential combinations; it would be
difficult to cram meaningful error descriptions (end user
description, error code, application state etc) into a poor heartbeat.
Patrick
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|