Re: [Aglets-users] Basic Aglets.net Effort

[RAB <ra...@co...>]

Thomas Calivera wrote:

[Analysis removed for brevity]

>
> I am leaning towards this alternative as the initial implementation after
> walking through the above. If we do the alternative first, the former
> implementation is still useful at a later date if we want to roll a
> distribution that registers itself with the monitor upon startup. I'll stop
> here before going into the recovery process on restart or network isolation.
>
> Your thoughts? Cheryl? Others? If you are reading this, you are probably a
> potential user of this, so what works best for you?

I'm a firm believer in iterative design processes.  The web page registration
reduces some of the complexity and will get a system running.  It should provide
a solid basis for development and experimentation, and there's no barriers for
implementing a more automated registration process later.  I vote for putting
some prototype code behind this one.  I, for one, need to get some more
experience with remote messaging.

The recovery process could get interesting.  I am currently running with the
following scenarios.  First, the monitoring server goes down.  Second, the
remote server goes down.  These two are due to a system/software failure of some
kind.  Third is network isolation i.e. the servers are running by someone drove
a backhoe throuh UUnet's fiber plant. <g>  Lastly, the gracefull shutdown of the
monitor or the remote.  I need to give these some more thought.  Opinions
anyone?  Any scenario I've missed?

Cheers,

// RAB