-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 4:07 PM, Peter Saint-Andre wrote:
> On 4/21/09 2:58 PM, JiYí Zárevúcký wrote:
>> 2009/4/21 Peter Saint-Andre :
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 4/21/09 12:57 PM, JiYí Zárevúcký wrote:
2009/4/21 Peter Sain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 4:31 PM, Jiří Zárevúcký wrote:
> 2009/4/22 Peter Saint-Andre :
>>> There could be another problem, though. If the roster got reverted,
>>> some client could update it up to the original sequence number or
>>> further. Then if some client tha
> But if several people don't expect that under the title "Multi-User
> Gaming" then we should look for a more appropriate title.
Cool, we're in agreement then. I think the key point here is to contrast it
with multiuser games where players use XMPP for chat and negotiate server
connections via
2009/4/22 Peter Saint-Andre :
>>
>> There could be another problem, though. If the roster got reverted,
>> some client could update it up to the original sequence number or
>> further. Then if some client that wasn't used for long time came
>> online, it could receive wrong updates.
>
> I think it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've created a new list for discussions related to gaming applications
of XMPP technologies. Subscribe here:
http://mail.jabber.org/mailman/listinfo/gaming
mailto:gaming-subscr...@xmpp.org
Peter
- --
Peter Saint-Andre
https://stpeter.im/
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 2:58 PM, Jiří Zárevúcký wrote:
> 2009/4/21 Peter Saint-Andre :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 4/21/09 12:57 PM, Jiří Zárevúcký wrote:
>>> 2009/4/21 Peter Saint-Andre :
I propose the following implementation
2009/4/21 Peter Saint-Andre :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 4/21/09 12:57 PM, Jiří Zárevúcký wrote:
>> 2009/4/21 Peter Saint-Andre :
>>> I propose the following implementation note:
>>>
>>> In some conditions, an XMPP client or server might know that the
>>> sequence
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 12:57 PM, Jiří Zárevúcký wrote:
> 2009/4/21 Peter Saint-Andre :
>> I propose the following implementation note:
>>
>> In some conditions, an XMPP client or server might know that the
>> sequence numbering is invalid (e.g., because of a c
2009/4/21 Peter Saint-Andre :
> I propose the following implementation note:
>
> In some conditions, an XMPP client or server might know that the
> sequence numbering is invalid (e.g., because of a catastrophic server
> failure). In these cases, the entity that discovers the problem
> SHOUL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 7:53 AM, Peter Saint-Andre wrote:
> On 4/21/09 7:07 AM, Dave Cridland wrote:
>> On Fri Apr 17 22:03:57 2009, XMPP Extensions Editor wrote:
>
>> 2) There are cases where the sequence numbering can be known to have
>> broken, for example, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 8:47 AM, Peter Saint-Andre wrote:
> On 4/21/09 7:53 AM, Peter Saint-Andre wrote:
>> On 4/21/09 7:07 AM, Dave Cridland wrote:
>
>>> 3) We borrow text from RFC 4551, which has IPR implications.
>> I think that we borrow a concept from 4551 b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 7:53 AM, Peter Saint-Andre wrote:
> On 4/21/09 7:07 AM, Dave Cridland wrote:
>
>> 3) We borrow text from RFC 4551, which has IPR implications.
>
> I think that we borrow a concept from 4551 but perhaps not exact text.
> I'll check on that.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/21/09 7:07 AM, Dave Cridland wrote:
> On Fri Apr 17 22:03:57 2009, XMPP Extensions Editor wrote:
>> Version 0.7 of XEP-0237 (Roster Versioning) has been released.
>
> A couple of minor points.
>
> 1) Roster pushes sent by the server MUST be sent
On Fri Apr 17 22:03:57 2009, XMPP Extensions Editor wrote:
Version 0.7 of XEP-0237 (Roster Versioning) has been released.
A couple of minor points.
1) Roster pushes sent by the server MUST be sent in order of the ver
attribute.
There's a whole horrible mess that occurs if any pushes are se
14 matches
Mail list logo
