On 05/30/2012 01:30 AM, Peter Saint-Andre wrote:
> On 5/29/12 12:27 PM, Sergey Dobrov wrote:
>> On 05/30/2012 12:48 AM, Kim Alvefur wrote:
>>> On Wed, 2012-05-30 at 00:47 +0700, Sergey Dobrov wrote:
I don't actually understand how this XEP can work with generic (not PEP)
pubsub? I have to
On 5/29/12 12:27 PM, Sergey Dobrov wrote:
> On 05/30/2012 12:48 AM, Kim Alvefur wrote:
>> On Wed, 2012-05-30 at 00:47 +0700, Sergey Dobrov wrote:
>>> I don't actually understand how this XEP can work with generic (not PEP)
>>> pubsub? I have to subscribe to each pubsub service which nodes I have
>>
On 05/30/2012 12:48 AM, Kim Alvefur wrote:
> On Wed, 2012-05-30 at 00:47 +0700, Sergey Dobrov wrote:
>> I don't actually understand how this XEP can work with generic (not PEP)
>> pubsub? I have to subscribe to each pubsub service which nodes I have
>> subscribed to? It's an overhead, isn't it?
>
On Wed, 2012-05-30 at 00:47 +0700, Sergey Dobrov wrote:
> I don't actually understand how this XEP can work with generic (not PEP)
> pubsub? I have to subscribe to each pubsub service which nodes I have
> subscribed to? It's an overhead, isn't it?
Isn't the reverse, ie the pubsub service needs to
I don't actually understand how this XEP can work with generic (not PEP)
pubsub? I have to subscribe to each pubsub service which nodes I have
subscribed to? It's an overhead, isn't it?
On 05/29/2012 11:42 PM, XMPP Extensions Editor wrote:
> Version 0.3 of XEP-0312 (PubSub Since) has been released
Version 0.3 of XEP-0312 (PubSub Since) has been released.
Abstract: This specification defines a publish-subscribe feature that enables a
subscriber to automatically receive pubsub and PEP notifications since the last
logout time of a specific resource.
Changelog: Corrected namespace to use nam
pls unsubscribe me from your emails
From: Joe Hildebrand
To: XMPP Standards
Sent: Wednesday, March 14, 2012 3:34 AM
Subject: Re: [Standards] UPDATED: XEP-0312 (PubSub Since)
On 3/13/12 2:55 AM, "Sergey Dobrov" wrote:
> On 03/13/2012
On 03/15/2012 06:30 AM, Peter Saint-Andre wrote:
> On 3/14/12 10:42 AM, Sergey Dobrov wrote:
>> On 03/14/2012 09:28 PM, Joe Hildebrand wrote:
>>>
>>> It could be used by non-PEP pubsub, by, for example, sending an ago stanza
>>> in your subscribe, or by translating it into a subscription option.
>>
On 03/15/2012 09:06 AM, Joe Hildebrand wrote:
> On 3/14/12 10:42 AM, "Sergey Dobrov" wrote:
>
> Please make sure you've seen the contacts portion of XEP-292 as well:
>
> http://xmpp.org/extensions/xep-0292.html#contacts
>
> This part is about storing a list of contacts for *myself*, so none of
On 3/14/12 10:42 AM, "Sergey Dobrov" wrote:
> On 03/14/2012 09:28 PM, Joe Hildebrand wrote:
>>
>> It could be used by non-PEP pubsub, by, for example, sending an ago stanza
>> in your subscribe, or by translating it into a subscription option.
>
> Yeah, I just mean that it'd be cool to describe
On 3/14/12 10:42 AM, Sergey Dobrov wrote:
> On 03/14/2012 09:28 PM, Joe Hildebrand wrote:
>>
>> It could be used by non-PEP pubsub, by, for example, sending an ago stanza
>> in your subscribe, or by translating it into a subscription option.
>
> Yeah, I just mean that it'd be cool to describe such
On 03/14/2012 09:28 PM, Joe Hildebrand wrote:
>
> It could be used by non-PEP pubsub, by, for example, sending an ago stanza
> in your subscribe, or by translating it into a subscription option.
Yeah, I just mean that it'd be cool to describe such way because it will
probably use iq and not prese
On 3/14/12 1:32 AM, "Sergey Dobrov" wrote:
> On 03/14/2012 07:04 AM, Joe Hildebrand wrote:
>> On 3/13/12 2:55 AM, "Sergey Dobrov" wrote:
>>
>>> Actually, it's
>>> not clear how pubsub service will receive the presence in case of pubsub
>>> (and not presence) subscription.
>>
>> PEP.
>
> So th
On 03/14/2012 07:04 AM, Joe Hildebrand wrote:
> On 3/13/12 2:55 AM, "Sergey Dobrov" wrote:
>
>> Actually, it's
>> not clear how pubsub service will receive the presence in case of pubsub
>> (and not presence) subscription.
>
> PEP.
So the title of the XEP can mislead. The other thing that the s
On 3/13/12 2:55 AM, "Sergey Dobrov" wrote:
> On 03/13/2012 12:52 AM, Joe Hildebrand wrote:
>>
>>> Another still uncovered thing is how to determine missed notifications
>>> in the case of connection failures.
>>
>> This is really an implementation detail of how the client sets the time in
>> th
On 03/13/2012 12:52 AM, Joe Hildebrand wrote:
>
>> Another still uncovered thing is how to determine missed notifications
>> in the case of connection failures.
>
> This is really an implementation detail of how the client sets the time in
> the ago.
>
Sure. But how it's suggested to the client
On 3/11/12 4:53 AM, "Sergey Dobrov" wrote:
> Still have many questions to the XEP.
>
> It's needed to add some examples of notifications to be sent:
>
> 1. How to determine that the notification is from the past and not the
> current notification?
The intent is that it doesn't matter; the clie
Still have many questions to the XEP.
It's needed to add some examples of notifications to be sent:
1. How to determine that the notification is from the past and not the
current notification?
2. Will the server send retracts or node configuration changes
notifications from the past?
Possibly, t
Still have many questions to the XEP.
It's needed to add some examples of notifications to be sent:
1. How to determine that the notification is from the past and not the
current notification?
2. Will the server send retracts or node configuration changes
notifications from the past?
Possibly, t
Version 0.2 of XEP-0312 (PubSub Since) has been released.
Abstract: This specification defines a publish-subscribe feature that enables a
subscriber to automatically receive pubsub and PEP notifications since the last
logout time of a specific resource.
Changelog: Replaced jabber:iq:last with a
20 matches
Mail list logo
