Android - Application Level socket.io

up vote
0
down vote

favorite

I'm working with Socket, using Socket.io Android Library & it's implemented well and working successfully.
It's done, But it's in only single activity.

Now I want socket implementation in the entire application.
Something more reliable and easy.
I need socket listeners and methods to emit and receive in a single place so don't have to write everywhere.

I want a class where I can put all socket code and access it from anywhere and listen to that class all the time & pass an event to other Activities or Fragment if I receive anything in a socket.

What should be a good solution for this?

Thanks

asked Nov 19 at 14:16

Mayur Patanvadiya

add a comment |

up vote
0
down vote

favorite

I'm working with Socket, using Socket.io Android Library & it's implemented well and working successfully.
It's done, But it's in only single activity.

I want a class where I can put all socket code and access it from anywhere and listen to that class all the time & pass an event to other Activities or Fragment if I receive anything in a socket.

What should be a good solution for this?

Thanks

asked Nov 19 at 14:16

Mayur Patanvadiya

add a comment |

up vote
0
down vote

favorite

I'm working with Socket, using Socket.io Android Library & it's implemented well and working successfully.
It's done, But it's in only single activity.

I want a class where I can put all socket code and access it from anywhere and listen to that class all the time & pass an event to other Activities or Fragment if I receive anything in a socket.

What should be a good solution for this?

Thanks

asked Nov 19 at 14:16

Mayur Patanvadiya

I'm working with Socket, using Socket.io Android Library & it's implemented well and working successfully.
It's done, But it's in only single activity.

I want a class where I can put all socket code and access it from anywhere and listen to that class all the time & pass an event to other Activities or Fragment if I receive anything in a socket.

What should be a good solution for this?

Thanks

android sockets design-patterns socket.io

asked Nov 19 at 14:16

Mayur Patanvadiya

asked Nov 19 at 14:16

Mayur Patanvadiya

asked Nov 19 at 14:16

Mayur Patanvadiya

asked Nov 19 at 14:16

Mayur Patanvadiya

asked Nov 19 at 14:16

Mayur Patanvadiya

add a comment |

1 Answer
1

active

oldest

votes

up vote
2
down vote

You should try moving your SocketIO implementation to a Service, it looks like the right use case to do it.

here you can find a post on how to implement it and do the communication activity/service
Ways to communicate between activity and service

answered Nov 19 at 14:34

Daniel Loaiza

366

1

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

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',
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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376542%2fandroid-application-level-socket-io%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

You should try moving your SocketIO implementation to a Service, it looks like the right use case to do it.

here you can find a post on how to implement it and do the communication activity/service
Ways to communicate between activity and service

answered Nov 19 at 14:34

Daniel Loaiza

366

1

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

add a comment |

up vote
2
down vote

You should try moving your SocketIO implementation to a Service, it looks like the right use case to do it.

here you can find a post on how to implement it and do the communication activity/service
Ways to communicate between activity and service

answered Nov 19 at 14:34

Daniel Loaiza

366

1

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

add a comment |

up vote
2
down vote

You should try moving your SocketIO implementation to a Service, it looks like the right use case to do it.

here you can find a post on how to implement it and do the communication activity/service
Ways to communicate between activity and service

answered Nov 19 at 14:34

Daniel Loaiza

366

You should try moving your SocketIO implementation to a Service, it looks like the right use case to do it.

here you can find a post on how to implement it and do the communication activity/service
Ways to communicate between activity and service

answered Nov 19 at 14:34

Daniel Loaiza

366

answered Nov 19 at 14:34

Daniel Loaiza

366

answered Nov 19 at 14:34

Daniel Loaiza

366

answered Nov 19 at 14:34

Daniel Loaiza

366

1

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

add a comment |

1

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

Note: If your app targets API level 26 or higher, the system imposes restrictions on running background services when the app itself isn't in the foreground. In most cases like this, your app should use a scheduled job instead.
– Mayur Patanvadiya
Nov 20 at 13:05

add a comment |

draft saved

draft discarded

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.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Nsryjdtyk