Do you have any opinion on the disco for individual games?
I see basically three ways to do it:
1. include games in normal disco as feature
2. use info/item nodes in normal disco
3. some "own" third way, as we did
Number 1 could blow up the disco response considerably, while Number 2
and 3 allow for a separate query for games. Unfortunately, I can't come
up with a nice way to do Number 2.
Our current solution is very similar to a disco#items query (e.g. MUC
room query). Are there any good reasons not to do it that way?
I would do it as option 2, where the main disco info would just have a
feature of "http://jabber.org/protocol/games";, then if people want to
retrieve a full list of the games you support they would do a disco#info
query on the special node for games (http://jabber.org/protocol/games), e.g.
<iq from='[EMAIL PROTECTED]/garden' to='[EMAIL PROTECTED]/balcony'
id='req1' type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='http://jabber.org/protocol/games'/>
</iq>
<iq from='[EMAIL PROTECTED]/garden' to='[EMAIL PROTECTED]/balcony'
id='req1' type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'
node='http://jabber.org/protocol/games'>
<feature var='http://jabber.org/protocol/games/tictactoe'/>
<feature var='http://jabber.org/protocol/games/chess'/>
</query>
</iq>
This allows easy use of disco without bloating the main response.
Richard
