> Date: Sun, 20 Sep 2009 15:47:55 +0300
> From: [email protected]
> To: [email protected]
> Subject: Re: [PubSub] [Fwd: Re: [Standards] Pubsub temporary subscriptions]
>
> On Sun, Sep 20, 2009 at 9:11 AM, Christophe Romain
> <[email protected]> wrote:
Nathan suggested a value of 'presence' for pubsub#expire for this. That
should be specified at some point.
+1
> A node configuration option for this would be smarter. Tigase implemented
> such a feature recently:
> http://projects.tigase.org/pubsub/trac/changeset/229
> I've explained why a node config is better than a subscription option here:
> http://mail.jabber.org/pipermail/pubsub/2009-June/000240.html
I think you will see cases where both are valid (node and subscription),
depending on the context
in which the node is being used or the data it stores. I agree though that the
repercussions of not having it on the node can be pretty high in an openly
accessible system. You would obviously have
to put custom code in the server to 'fix' this problem in your case.
Actually, I wrote a plugin for OpenFire to do the same thing for a project I
was working on.
I think you could see the need for the subscription based approach as well
though. For example,
if a node was being used to publish notifications of news events, and the node
is configured to
publish when the user is not present, it would allow clients to determine how
they want to consume
the events. Where some may want all events, even when offline, others may only
want them
when online. This is a case where the node doesn't care how things are being
consumed, so the
onus is on the consumer to specify.
_________________________________________________________________
We are your photos. Share us now with Windows Live Photos.
http://go.microsoft.com/?linkid=9666047
