On Sun, Sep 6, 2009 at 1:27 PM, Fabio Forno<[email protected]> wrote: > I'm peeking in google wave specs and I see that updates are > distributed through pubsub events in a standard way (see > http://www.waveprotocol.org/draft-protocol-spec#iq-elements-update-stream) > + xep-184 for acks. This leads to more or less the same behavior than > <iq/> stanzas but I'm wondering if it is a good idea to replicate over > <message/> stanzas what we indeed expect from <iq/> ones, since it > becomes more complex tracking errors in situations like when the > recipient resource goes down. Therefore Wave use case makes me think > that there is real world need of acks and for that a delivery profile > over <iq/> would be more indicated
I think, really, what is needed here is just to go about business as normal, but use 198 at the stream level, so you know that everything's going to get through (albeit with no guarantee about when). /K
