Bonjour service not resolved after sleeping
I'm working on a Service/Client model whereas I have a Server application running on PC and several clients running on different platform including PC, iOS app.
The Server broadcast itself using Bonjour, everything works great so far.
However, when leaving the iOS device to sleep and don't touch it for a while then open it again. The app could not resolve the Service from Main. The service is still in the network because it can be discovered using the PC client.
The only way for client to realize the service is to restart the Server on PC which will broadcast again.
Same thing happen to Bonjour Service Browser app , is this something related to caching on iOS device?
Any idea are much appreciated!!!
ios swift bonjour pc
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
add a comment |
I'm working on a Service/Client model whereas I have a Server application running on PC and several clients running on different platform including PC, iOS app.
The Server broadcast itself using Bonjour, everything works great so far.
However, when leaving the iOS device to sleep and don't touch it for a while then open it again. The app could not resolve the Service from Main. The service is still in the network because it can be discovered using the PC client.
The only way for client to realize the service is to restart the Server on PC which will broadcast again.
Same thing happen to Bonjour Service Browser app , is this something related to caching on iOS device?
Any idea are much appreciated!!!
ios swift bonjour pc
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45
add a comment |
I'm working on a Service/Client model whereas I have a Server application running on PC and several clients running on different platform including PC, iOS app.
The Server broadcast itself using Bonjour, everything works great so far.
However, when leaving the iOS device to sleep and don't touch it for a while then open it again. The app could not resolve the Service from Main. The service is still in the network because it can be discovered using the PC client.
The only way for client to realize the service is to restart the Server on PC which will broadcast again.
Same thing happen to Bonjour Service Browser app , is this something related to caching on iOS device?
Any idea are much appreciated!!!
ios swift bonjour pc
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
I'm working on a Service/Client model whereas I have a Server application running on PC and several clients running on different platform including PC, iOS app.
The Server broadcast itself using Bonjour, everything works great so far.
However, when leaving the iOS device to sleep and don't touch it for a while then open it again. The app could not resolve the Service from Main. The service is still in the network because it can be discovered using the PC client.
The only way for client to realize the service is to restart the Server on PC which will broadcast again.
Same thing happen to Bonjour Service Browser app , is this something related to caching on iOS device?
Any idea are much appreciated!!!
ios swift bonjour pc
ios swift bonjour pc
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
asked Nov 22 '18 at 10:43
Chinh NguyenChinh Nguyen
13127
13127
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45
add a comment |
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45
add a comment |
0
active
oldest
votes
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%2f53429154%2fbonjour-service-not-resolved-after-sleeping%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53429154%2fbonjour-service-not-resolved-after-sleeping%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
According to Apple doc [developer.apple.com/library/archive/documentation/Cocoa/… (here), it might be something to do with TTL (time-to-live) which is default to 2 minutes. Any idea on how we can keep the service broadcasting through out the app life-cycle?
– Chinh Nguyen
Nov 26 '18 at 10:45