On 15 March 2011 12:36, Jonathan Schleifer <js-xmpp-standa...@webkeks.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > Hi. > > Just having looked at my offline storage, I saw that chat states are stored > by the server. But of course they are, as the type is chat and thus the > server has to store them. > > Thinking about it, wouldn't it make sense to set the type to headline? > Are there any reasons why we couldn't just test how many clients still work > correctly if you just change the type to headline and if most of the clients > still accept it change the XEP? > > And while we're at it, wouldn't the same make sense for PEP? >
Thanks for bringing this up. Chat states cause issues in other areas too - MUC history for example (however in this case they have type='groupchat'). We don't want to special-case the chat states xmlns in all these places. For one-to-one chats 'headline' may be the answer. For MUC the answer may be to not store anything without a <body/>. For PEP I think the recommendation is to broadcast with type='headline', but you technically shouldn't receive PEP notifications while offline anyway. For pubsub sometimes you want type='headline' and sometimes you don't. And this is all before we touch on the topic of archiving... Perhaps I'm mistaken in viewing this as a generic problem, but it seems like we have a number of stores/caches in XMPP, and how various XEPs interact with them isn't well-defined, leading to non-optimal behaviour as you've discovered. Regards, Matthew
