Quoting [Ceriel Jacobs] (Dec 13 2007):
Andre Merzky wrote:
Please note that the wildcard issue is REALLY the last known issue - as soon as we have that settled the spec is out. So if you have discovered anything else... ;)
Well, it is not as if I have a supply of them and just report a couple of them whenever I feel like it :-)
So, you mean, your private list of issues is indeed finite? Good news!! :-)
But, I just noticed another one: in the monitoring package, metric class, there is a sentence that states that
The metric |type|s are the same as defined for attributes, and the metric |value|s are to be formatted as described for the respective attribute types.
Ah, well, finite + n ... ;-)
But what about the Trigger type? This is not mentioned as one of the attribute types. In fact, it is never really specified what a 'Trigger' is.
Ah, good one, will fix that. In short: 'Checkpoint' would be a good example for a trigger. Its not boolean: you never notify an application 'Do no checkpoint now!' - but you use the metric to trigger a checkpoint 'Checkpoint now!'. I guess this is equivalent to an attribute who's existence or absence carries semantic meaning (e.g. 'Checkpointable'). That, however, maps pretty nicely to boolean attributes in all cases I can think of ('Checkpointable=yes'). Does that make sense? Thanks, Andre.
Cheers, Ceriel
-- No trees were destroyed in the sending of this message, however, a significant number of electrons were terribly inconvenienced.