Kevin Smith wrote:
Yes, I think you're right. So maybe we just need to define gone/ more
carefully?
Seems so to me.
Client could determine that user is gone by using same technology it
does to answer POKE requests ;)
--
Maciek
xmpp:[EMAIL PROTECTED]
Kevin Smith wrote:
Yes, I think you're right. So maybe we just need to define gone/ more
carefully?
Seems so to me.
Well, gone/ is defined as the user has effectively ended their
participation in the chat session -- i.e., the user has not interacted
with the chat interface, system, or
On Wed, Jul 16, 2008 at 3:52 PM, Peter Saint-Andre [EMAIL PROTECTED] wrote:
Well, gone/ is defined as the user has effectively ended their
participation in the chat session -- i.e., the user has not interacted with
the chat interface, system, or device for a relatively long period of time
Kevin Smith wrote:
On Wed, Jul 16, 2008 at 3:52 PM, Peter Saint-Andre [EMAIL PROTECTED] wrote:
Well, gone/ is defined as the user has effectively ended their
participation in the chat session -- i.e., the user has not interacted with
the chat interface, system, or device for a relatively long
Peter Saint-Andre wrote:
Someone pointed out to me the following discrepancy between
XEP-0085 and XEP-0201...
XEP-0085 says:
Upon receiving a gone/ event, a client MUST NOT re-use
the same Thread ID and MUST generate a new Thread ID for
any subsequent chat messages sent to the
Hello,
for my own I don't really know these XEP, so I will base my idea on
what you wrote and also my logic. In a simple way, I think a thread
could indeed be tied to a single chat window.
But in the real use, there are 2 points I think important to raise:
1/ nowaydays most clients have the
On Wed, Jun 11, 2008 at 12:04 AM, Peter Saint-Andre [EMAIL PROTECTED] wrote:
XEP-0085 says:
Upon receiving a gone/ event, a client MUST NOT re-use
the same Thread ID and MUST generate a new Thread ID for
any subsequent chat messages sent to the conversation
partner.
XEP-0201 says:
Kevin Smith wrote:
On Wed, Jun 11, 2008 at 12:04 AM, Peter Saint-Andre [EMAIL PROTECTED] wrote:
XEP-0085 says:
Upon receiving a gone/ event, a client MUST NOT re-use
the same Thread ID and MUST generate a new Thread ID for
any subsequent chat messages sent to the conversation
partner.
Yes, I think you're right. So maybe we just need to define gone/ more
carefully?
Seems so to me.
/K
Someone pointed out to me the following discrepancy between
XEP-0085 and XEP-0201...
XEP-0085 says:
Upon receiving a gone/ event, a client MUST NOT re-use
the same Thread ID and MUST generate a new Thread ID for
any subsequent chat messages sent to the conversation
partner.
XEP-0201
10 matches
Mail list logo
