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
XEP-0198: Stream Management #281
Comments
I was finish this feature, could I share my codes ? ObjColumnist |
Ive started to work on this, but your welcome to send me what you have done. |
Hi ObjColumnist, |
Thanks I will take a look :) |
I have a rather immediate need to implement XEP-0198 into my current project. Is there a way to be included in the development/implementation of this protocol into this framework? I would be very interested in contributing. Thanks! |
To be specific, I've dropped in nguyenthanhhai's code for XEP-0198 into my project, but the latest revision is missing a required XMPPMessageAdditions.h and supporting code. At the very least, is it possible to receive a copy of these required files? Thanks again. |
Thank you very much! -=Kevin On Fri, Mar 7, 2014 at 11:00 AM, NeXT Steve notifications@github.comwrote:
|
I've implemented the code, which compiles properly and my original code Thanks again for making this available to me. -=Kevin On Fri, Mar 7, 2014 at 11:01 AM, Kevin Pinkerman kpinkerman@gmail.comwrote:
|
Let's implement two methods:
XMPPStreanManagement does not manage the message in the stream but you can track the message sending/receiving statge to resend failed message or devivered messages. |
After working with this a bit more, I've noticed that my Tigase server is now successfully showing data packets. I am noticing, though, that it is using namespace "urn:ccping:sm" when I activate stream management instead of the expected namespace "urn:xmpp:sm:3". Am I getting the setup wrong on this? |
I think I've found the issue. It looks like the stream management protocol listed here is for a custom implementation of stream management. I'm going to change the urn to the standard protocol naming convention and reattempt. |
OK. I have been able to get the server to enable stream management, but r & a elements are not being sent/received by this library. I am currently using sendElement: from the XMPPStream object. Is there a different function to enable the req/ack process? In case I have set up streamMangagement wrong, I have included my current setup:
Whatever help you can provide would be greatly appreciated. |
Any idea why the req/ack process is not working in this implementation? Thank you. |
#342 check my implementation and give some code review |
I just pushed commit 29dc0ff "Initial support for XEP-0198 (stream management)"
I added XMPPCustomBinding protocol, which now allows for this outside of XMPPStream. I hope you'll be pleasantly surprised with the API. |
Great! Thank you so much! |
Are there any milestones for this? XEP-0198 is currently not supported as evident from the supported extensions page. Any realistic date for when this will be supported? Thanks! |
Hi , is there any way to enable XEP-0198 in ejabberd version 2.1.10? |
No description provided.
The text was updated successfully, but these errors were encountered: