-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BOSH support #40
Comments
Hi Andreas.
I can't help you there. It feels like my work on the XMPP was in the
previous life - I have already forgotten everything. Hopefully someone else
can.
Best regards,
Alexey Nezhdanov.
Am Fr., 13. Nov. 2020 um 21:42 Uhr schrieb Andreas Motl <
notifications@github.com>:
… Dear @snakeru <https://github.com/snakeru>, @normanr
<https://github.com/normanr> and @Neustradamus
<https://github.com/Neustradamus>,
in order to add more meat to #39
<#39>, I just checked the SleekXMPP
<https://github.com/fritzy/SleekXMPP> and Slixmpp
<https://github.com/poezio/slixmpp> libraries for support of BOSH (
XEP-0124 <https://xmpp.org/extensions/xep-0124.html>, XEP-0206
<https://xmpp.org/extensions/xep-0206.html>).
As I am not involved into the nitty gritty details of the XMPP
specification in any way, I humbly asking you whether BOSH is still a thing
these days? I can well see that xmpppy has some support for that which
might have been slightly improved through #23
<#23>.
On the other hand, there are absolute no references to "bosh", "124" or
"206 when searching through the Slixmpp code base. When looking at
SleekXMPP (which has already been archived by its maintainer), there is
only fritzy/SleekXMPP#160 <fritzy/SleekXMPP#160>
and fritzy/SleekXMPP#476 <fritzy/SleekXMPP#476>,
which also outline that BOSH might not be supported.
According to horazont/aioxmpp#252
<https://github.com/horazont/aioxmpp/issues/252> and horazont/aioxmpp#18
<https://github.com/horazont/aioxmpp/issues/18>, aioxmpp
<https://github.com/horazont/aioxmpp> also doesn't support neither BOSH
nor Websockets. python-nbxmpp <https://dev.gajim.org/gajim/python-nbxmpp>
replaced BOSH with Websocket at its 1.0.0 release (18 June 2020).
Apologies for asking such questions, I have only used xmpppy for basic
operations so far and would like to gain more knowledge about its
featureset from you.
With kind regards,
Andreas.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#40>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARXUL4K3CEXM2YB52EEXLSPWKZZANCNFSM4TVA5FJA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear @snakeru, @normanr and @Neustradamus,
in order to add more meat to #39, I just checked the SleekXMPP and Slixmpp libraries for support of BOSH (XEP-0124, XEP-0206).
As I am not involved into the nitty gritty details of the XMPP specification in any way, I humbly asking you whether BOSH is still a thing these days? I can well see that xmpppy has some support for that which might have been slightly improved through #23.
On the other hand, there are absolute no references to "bosh", "124" or "206 when searching through the Slixmpp code base. When looking at SleekXMPP (which has already been archived by its maintainer), there is only fritzy/SleekXMPP#160 and fritzy/SleekXMPP#476, which also outline that BOSH might not be supported.
According to https://github.com/horazont/aioxmpp/issues/252 and https://github.com/horazont/aioxmpp/issues/18, aioxmpp also doesn't support neither BOSH nor Websockets. python-nbxmpp replaced BOSH with Websocket at its 1.0.0 release (18 June 2020).
Apologies for asking such questions, I have only used xmpppy for basic operations so far and would like to gain more knowledge about its featureset from you.
With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: