How to use stream management acks in xmpp.js (in react-native) with MongooseIM (as chat server)?
I am using xmpp.js as xmpp chat client inside react-native for both android+ios with MongooseIM as chat server. I want to implement stream management acks in the App. But according to the issue#540, xmpp.js doesn't officially support stream management for now. What can be the alternate to this?
I need the stream management module only to send/receive acks between c2s and s2s. Please guide.
react-native xmpp ejabberd mongoose-im node-xmpp
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
add a comment |
I am using xmpp.js as xmpp chat client inside react-native for both android+ios with MongooseIM as chat server. I want to implement stream management acks in the App. But according to the issue#540, xmpp.js doesn't officially support stream management for now. What can be the alternate to this?
I need the stream management module only to send/receive acks between c2s and s2s. Please guide.
react-native xmpp ejabberd mongoose-im node-xmpp
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
add a comment |
I am using xmpp.js as xmpp chat client inside react-native for both android+ios with MongooseIM as chat server. I want to implement stream management acks in the App. But according to the issue#540, xmpp.js doesn't officially support stream management for now. What can be the alternate to this?
I need the stream management module only to send/receive acks between c2s and s2s. Please guide.
react-native xmpp ejabberd mongoose-im node-xmpp
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
I am using xmpp.js as xmpp chat client inside react-native for both android+ios with MongooseIM as chat server. I want to implement stream management acks in the App. But according to the issue#540, xmpp.js doesn't officially support stream management for now. What can be the alternate to this?
I need the stream management module only to send/receive acks between c2s and s2s. Please guide.
react-native xmpp ejabberd mongoose-im node-xmpp
react-native xmpp ejabberd mongoose-im node-xmpp
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
asked Nov 12 '18 at 7:03
Shubham1164Shubham1164
627
627
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Stream Management, if not available in your client library of choice, is somewhat complex to implement - though definitely would be welcome by the open source community ;)
XMPP Ping is a simpler alternative to detect broken connections. It's available in a range of servers including MongooseIM and ejabberd. The idea is that any side of the connection sends a ping IQ - since IQs are standardised to require responses, if a response does not come in a predefined time interval, you can assume such a connection is dead. There's no protocol for message retransmission like with Stream Management, but if you're running with Message Archive Management (mod_mam) all the messages should be stored safely anyway.
Alternatively, as somebody has suggested in the issue you link, you could switch to Stanza.io which supports XEP-198.
answered Nov 13 '18 at 9:56
erszczerszcz
969615
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257285%2fhow-to-use-stream-management-acks-in-xmpp-js-in-react-native-with-mongooseim%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Stream Management, if not available in your client library of choice, is somewhat complex to implement - though definitely would be welcome by the open source community ;)
XMPP Ping is a simpler alternative to detect broken connections. It's available in a range of servers including MongooseIM and ejabberd. The idea is that any side of the connection sends a ping IQ - since IQs are standardised to require responses, if a response does not come in a predefined time interval, you can assume such a connection is dead. There's no protocol for message retransmission like with Stream Management, but if you're running with Message Archive Management (mod_mam) all the messages should be stored safely anyway.
Alternatively, as somebody has suggested in the issue you link, you could switch to Stanza.io which supports XEP-198.
answered Nov 13 '18 at 9:56
erszczerszcz
969615
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
add a comment |
Stream Management, if not available in your client library of choice, is somewhat complex to implement - though definitely would be welcome by the open source community ;)
XMPP Ping is a simpler alternative to detect broken connections. It's available in a range of servers including MongooseIM and ejabberd. The idea is that any side of the connection sends a ping IQ - since IQs are standardised to require responses, if a response does not come in a predefined time interval, you can assume such a connection is dead. There's no protocol for message retransmission like with Stream Management, but if you're running with Message Archive Management (mod_mam) all the messages should be stored safely anyway.
Alternatively, as somebody has suggested in the issue you link, you could switch to Stanza.io which supports XEP-198.
answered Nov 13 '18 at 9:56
erszczerszcz
969615
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
add a comment |
Stream Management, if not available in your client library of choice, is somewhat complex to implement - though definitely would be welcome by the open source community ;)
XMPP Ping is a simpler alternative to detect broken connections. It's available in a range of servers including MongooseIM and ejabberd. The idea is that any side of the connection sends a ping IQ - since IQs are standardised to require responses, if a response does not come in a predefined time interval, you can assume such a connection is dead. There's no protocol for message retransmission like with Stream Management, but if you're running with Message Archive Management (mod_mam) all the messages should be stored safely anyway.
Alternatively, as somebody has suggested in the issue you link, you could switch to Stanza.io which supports XEP-198.
answered Nov 13 '18 at 9:56
erszczerszcz
969615
Stream Management, if not available in your client library of choice, is somewhat complex to implement - though definitely would be welcome by the open source community ;)
XMPP Ping is a simpler alternative to detect broken connections. It's available in a range of servers including MongooseIM and ejabberd. The idea is that any side of the connection sends a ping IQ - since IQs are standardised to require responses, if a response does not come in a predefined time interval, you can assume such a connection is dead. There's no protocol for message retransmission like with Stream Management, but if you're running with Message Archive Management (mod_mam) all the messages should be stored safely anyway.
Alternatively, as somebody has suggested in the issue you link, you could switch to Stanza.io which supports XEP-198.
answered Nov 13 '18 at 9:56
erszczerszcz
969615
answered Nov 13 '18 at 9:56
erszczerszcz
969615
answered Nov 13 '18 at 9:56
erszczerszcz
969615
answered Nov 13 '18 at 9:56
erszczerszcz
969615
969615
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
add a comment |
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
Thanks for answering. I have tried to use stanza.io with react-native but it throws so many errors, it seems its not readily compatible with it. But I will give some tries on that.
– Shubham1164
Nov 13 '18 at 10:19
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257285%2fhow-to-use-stream-management-acks-in-xmpp-js-in-react-native-with-mongooseim%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
