Hello On Sat, Jan 12, 2008 at 07:16:19PM +0100, Torsten Grote wrote: > Michal 'vorner' Vaner said the following on 01/12/2008 05:53 PM: > > I would rather like to see the numbers negotiated than have > > variants like: > > 20x20-5 > > 40x40-5 > > and so on. > > Feel free to send me your proposal for a section which defines this.
Well, you can put something like <rules xmlns='http://jabber.org/protocol/games/checkers'> <width>20</width> <height>20</height> <strike>5</strike> <at-turn>X</at-turn> <me>O</me> </rules> into the invitation. No need for other section, right? > > Could be a nice example, thought. And you do not need to define much > > ;-): > > > > <tictactoe> > > X_O > > OOX > > ___ > > </tictactoe> > > > > (Again, I know, it's first version.) > > Well the XEP Game Support has a fictive example for saving Tic Tac Toe > using Data Forms. Your way is much shorter, but is useless for being an > example on how to save game states in general. I'm not an expert on this > and don't know what's the best way. Suggestions by long time XMPP > experts are welcome. Well, you need some defined mechanism for every separate game anyway. And what is in your namespace (the game's namespace) is your own thing, that's what namespaces are for. You can not get a general way to save a game. And you need to define a game's moves in it's own namespace anyway, so I see no reason why to worry about data forms, which are for adding means of transfering data without defining a separate protocol for every usecase. But you need to define the fields at last. -- _(){ _&_;};_ Michal 'vorner' Vaner
pgpUe8ZbmDVjT.pgp
Description: PGP signature
