I've just pushed a patch to XEP-0288 which makes it mandatory for XEP-0288 implementations using XEP-0220 signalling to also support dialback errors.

In addition, though, Fippo and I were discussing an alternative which we quite like, but it's not clear it needed.

The current specification works by the receiver advertising <bidi/>, and the sender indicating it use by sending a <bidi/> element.

What we discussed was that instead of the latter indication, the <bidi/> stream feature would indicate a willingness to handle stream features from the sender - so the sender would then send stream features (which MUST contain a <bidi/>, or else would imply the same).

What this would gives us would be a more flexible base, but it does incur a little extra complexity, so neither of us is sure - so I thought I'd float the idea here.

Any comments?

Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

Reply via email to