Mike Fitzpatrick wrote:
> So, the list of admin mtypes I have now is:
>
> hub.event.shutdown
> hub.event.register
> hub.event.unregister
> hub.event.mtype
> hub.event.metadata
>
> app.ping
> app.event.shutdown
>
> app.status str status string
> app.status.progress msgid,str progress string
> app.status.progress.percent msgid,float percentage
> completed (float)
> app.status.progress.timeLeft msgid,int est. time remaining
> (sec)
I'm happy enough with this list.
> Lastly, did we settle the question of whether users can extend
> the hub/app toplevel classes or are we saying e.g. that any app.*
> message
> is reserved for the spec? Can anyone imagine a use-case where they
> implement a hub and want to define their own hub.* mtype for some
> particular reason?
Did we discuss it? I don't see why we have to make the app.* class of messages special in any way. People should free to extend it I think. The hub.* messages... erm. Different matter I think. Not sure.
Al. Received on 2008-06-04Z10:20:09