[ticker-dev] Elvin presence specification draft

[Klaus Alexander Seistrup]

Martin Wanicki wrote:

> Sooooo here's my suggestion.
> 
> Status becomes a number.
>     Negative One       (-1)     = off-line
>     Zero	         ( 0 )    = Available
>     Positive Non-Zero	 (1..???) = some "Unavailable" status event

I'm sorry Martin, but I do not support your suggestion.

Because of Elvin's subscription language I feel that notifications
should target humans, not applications.  While it might be tedious
to do the initial programming if text parsing is involved, it needs
only be dealt with once, and notifications like 'Status: "Online"'
are more intuitive that 'Status: 1' (who's got the header files or
a reference card available when subscribing?).

I am aware that most, if not all, status subscriptions will be done
by clients apps, but I still believe that programmers should design
their applications as if humans were the subscribers.  In the long
run such an approach will improve the overall usability, IMHO.


  // Klaus

-- 
 ><>°	 vandag, môre, altyd saam