Hi! Sergei Golovan schrieb:
>I forgot to mention that since there is no reason to use only jid, node and >name attributes (query isn't a disco#items query) Tkabber expects the >following answer: > ><iq type='result' to='[EMAIL PROTECTED]/orchard'> > <offline xmlns='http://jabber.org/protocol/offline'> > <item > node='2003-02-27T22:49:17.008Z' > from='[EMAIL PROTECTED]/pda' > category='presence' > type='subscribe'/> > <item > node='2003-02-27T22:52:37.225Z' > name='[EMAIL PROTECTED]/balcony' > category='message' > type='chat'/> > <item > node='2003-02-27T22:52:51.270Z' > name='[EMAIL PROTECTED]/balcony' > category='message' > type='headline'/> > <item > node='2003-02-27T22:53:03.421Z' > name='[EMAIL PROTECTED]/balcony' > category='message' > type='normal'/> > <item > node='2003-02-27T22:53:13.925Z' > name='[EMAIL PROTECTED]/balcony' > category='message'/> > </query> ></iq> > > I think if you add attributes to existing protocols, you should use your own namespaces for this. The http://jabber.org/protocol/offline namespace does not know category nor type attributes. Also I client should not "expect" to get these attributes, but just use them as hints if it gets them. Tot kijk Matthias _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
