[standards-jig] jep-0039 (Statistics Gathering)
rkdavis at burninghorse.com
Sat Nov 9 06:22:30 UTC 2002
i've been rereading the jep and come the the conclusion it is currently
extremly limited in it's usefulness.
1. It is currently documented as a pull only namespace, however
there are circumstances when it would be nice if it were possible to
"subscribe" to a statistic and have it pushed to us every X seconds.
Should this be handled via pub/sub or should it be part of this jep?
2. The format of the name attribute limits it's usefulness and
flexibilty. In particular in might be desirable to take the a query to
a third level or deeper i.e. rather than just bandwidth/packets-in i
might want to split the packets-in into their particular type i.e.
<iq/>, <message/>, <presence/> or even further. Should this be handled
by using JANA to just create multiple ways of obtaining the same
statistic i.e. bandwidth/packets-in and packets/iq, packets/presence...
or should the name attribute extend to three or more levels i.e.
bandwidth/packets-in#iq, bandwidth/packets-in#presence... (or some
variation of this)
3. Perhaps there should be one type of non-numeric statistic to
allow queries such as last logged in jid, this would not be a list just
a simple string.?
all of the above complicate the implementation to varying degrees so
comments and suggestions please.
jid: ukscone at burninghorse.com
More information about the Standards