On Tue, Aug 05, 2008 at 11:28:25AM -0600, Peter Saint-Andre wrote:
> vatsarv wrote:
> >Hi Peter, Thanks for the quick response.
> >
> >The message type of 'headline' will solve my previous problem, but a
> >new problem has come up because of this.
> >
> >I went throught the xep-0160 to see how the headline messages are
> >treated if the client is offline. This XEP recommends not to store any
> >offline message.
> >This is where I have a problem. I dont want to lose the message
> >altogether.
> >(The notification I get is an important one and I can't afford to lose
> >it)
>
> So we need one of the following:
>
> (1) a pubsub subscription option to configure what kind of message you
> want to receive
>
> (2) a way to configure your IM account to keep or discard headlines if
> you're offline
>
> I prefer (1).
>
> >Also, what was the messagetype used for PubSub till now? I dont see any
> >message type in the XEP 0060.
>
> Right now, 'normal'.
I have always assumed that the message type was mostly used for
determining how a message with a <body/> (or XHTML-IM) would be
presented to the user. For publish-subscribe notification messages,
without direct human readable text elements, it doesn't really matter,
because a client would need to just interpret the event and then decide
on its presentation.
Also, the publish-subscribe specification was written explicitly to work
in non-IM settings, too, so XMPP IM might not even apply.
In that light, no message type ('normal') is a sane default. Wether or
not a server should store those offline is another discussion, but I do
like that behaviour in some cases.
A configuration option for the message type seems like a reasonable
approach, and I would then also have one in the node config, to set the
default for new subscriptions.
However, in the end, selecting how messages should be delivered, offline
or not, should maybe not be done on the message type alone. Advanced
Message Processing comes to mind.
--
Groetjes,
ralphm
