[ticker-dev] Elvin presence spec draft - request for comments

[Klaus Alexander Seistrup]

David Arnold wrote:

> perhaps we need to consider a generic concept of groups, rather
> than domains?

I vote for that one -- _and_ the user at domain naming scheme.

Using the ELVIN_ONLINE_STATUS* as an example, what if we add another
field called GROUPS that contains a semicolon separated (to keep the
semantics of {CHAT,NEWS}_GROUPS) list of contact groups that the user
is a member of?

Initially GROUPS would only contain one group, namely the user's own
domain, but he could then expand the list by becoming a member of
already established groups or he could create his own group.

(I'm still scratching my own itch.)

So instead of doing a

ELVIN_ONLINE_STATUS_REQUEST: 1
DOMAIN: "mydomain"

request to see what users are online in his own domain, a user would
issue a

ELVIN_ONLINE_STATUS_REQUEST: 1
DOMAIN: "mydomain"
GROUP: "mygroup"

request for each of the groups that he is currently a member of.  The
DOMAIN field is maintained for greater flexibility.

Although this scheme doesn't fully solve the problem of global
scalability, at least it would allow automagic online awareness
across domain boundaries.

Anyone?


  // Klaus

-- 
A man, just one -
also a fly, just one -
in the huge drawing room.