Hi Nathan, Thanks for the feedback! Not sure I get your comments though :( users can subscribe with both a resource or bare JID. In the end we "strip" the resource and subscribe the bare JID. Whe you say "normal" consumer, do you actually mean "normal" client? If so, yes, our API wasn't meant to be used with regular Jabber client (Gajim, PSI), since our approach is clearly to promote PubSub. However, if a user still wants to use his "normal" jabber account, he can still subscribe with what we call a "jabber" account (like he would do with gtalk for example). Maybe this is not clear, but we have 2 different things : - Jabber account (like gatlk) : can be used by normal clients.. - XMPP API (Pubsub) : can be used by devs to create their own channels that users can then use.
Thanks again for the feedback though! -- Julien Genestoux http://www.ouvre-boite.com http://blog.notifixio.us +1 (415) 254 7340 +33 (0)9 70 44 76 29 On Fri, Nov 7, 2008 at 11:25 AM, Nathan Fritz <[EMAIL PROTECTED]> wrote: > According to your example, you seem to suggest subscribing with a resource > and not a bare jid, which makes sense depending on the type of consumer. > Also, your updates do not include a <body /> and thus a "normal" consumer > wouldn't get much use out of this. So, if your target audience is > specialized consumers, this looks great! Otherwise, I have several > suggestions. > > _______________________________________________ > JDev mailing list > FAQ: http://www.jabber.org/discussion-lists/jdev-faq > Forum: http://www.jabberforum.org/forumdisplay.php?f=20 > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [EMAIL PROTECTED] > _______________________________________________ > >
_______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
