I’ll certainly take a look at it. At the very
least I’ll put it on my Ruby to-do list (somewhere
above the genetic algorithm for finding optimal
Spades-playing strategies, and below the Fox
interfaces for RubyRED and Socrates).
Might even be a possibility for the Texas Codefest.
Dont’ suppose you can make it to that? Weekend of
Aug 17, I think, according to David Alan Black.
Any little clarifying notes you can add to the
comments or docs will help… especially if I
try to add a “glitch scanning” feature to it.
The ruby-talk numbers are not predictable before
they come back from the mailing list, right?
We can take this offline if you want – unless
maybe someone wants to comment here.
Re glitch scanning, I’m just thinking out loud:
When we get a news message and pass it to the
ML, we could potentially verify that we get it
back from the ML later. Implies a database or
something. Probably overkill.
Opposite direction, ML to new-- basically
symmetrical I guess. Also implies a database.
Hmm. When we get a news or mail msg, what fields
might refer back to another message? Can we detect
oddities? The ruby-talk number would help, perhaps.
----- Original Message -----
From: “Dave Thomas” Dave@PragmaticProgrammer.com
To: “ruby-talk ML” firstname.lastname@example.org
Sent: Tuesday, July 16, 2002 1:34 PM
Subject: Re: Gateway healthy?
“Hal E. Fulton” email@example.com writes:
But if you did do such a thing, you could perhaps even list and ID the
refresh it every N minutes, and your monitor can be purely web-based
(and perhaps save a few bytes of RAM and some CPU cycles).
If you’d like to take this on, I’d be happy to integrate it. I could
send you the up to date scripts as a base (they’ve changed just a bit
since I sent you the ones for the book).