On Tue, Sep 15, 2009 at 6:50 PM, Peter Saint-Andre <[email protected]> wrote: > >> I can't figure how the pubsub service >> would suss out a full JID from a bare without doing unseemly things. > > Agreed. >
Perhaps I'm missing something, but a presence access model imho is enough, where is the complication? >>> Further: how much core delivery logic are we forcing onto the pubsub >>> service? >> >> In the case of IQ delivery, if the problems with bare JIDs can be >> solved somehow (including not allowing them to subscribe to nodes >> configured to deliver via IQ) then any existing XMPP fabric should be >> able to handle the routing normally, and the pubsub service would only >> need to handle IQ related errors in addition to their current chores. > > Correct. That is the appeal. > Yep that was the idea reuse something that works without overcomplicating pubsub >> All that being said, I'm not thrilled with the idea of IQ delivery. >> I'd think if you needed something like this then you should use some >> kind of message delivery verification (I know, I know, we've been over >> this a million times), presence based subscriptions, or something similar. > > /me nods Well, I've said above presence subscriptions are essential, sorry if I've missed the specify this detail. The problem is that they don't completely solve the problem of reliability since I may send a message just before receiving an unavailable, not to mention flaky connections... bye -- Fabio Forno, Bluendo srl http://www.bluendo.com jabber id: [email protected]
