We have developed a NodeJS based chat application (Android application) with SocketIO.
But we notice 2 big problems :
1. Excessive data consumption (for 10 minutes the app consum more than 30 Mo even on background)
2. The untimely disconnection of the socket. We are obliged to restart the application to continue the chat
The architecture used is :
-- Database : MySQL
-- Web Server : Apache
-- Application server : proprietary server entirely developed in NodeJS with SocketIO
-- OS : Linux Ubuntu
We're looking for someone who can help us to resolv those issues.
*****************************************************************************************************
FRANÇAIS
*****************************************************************************************************
Nous avons développé une application de chat basée sur NodeJS (application Android) avec SocketIO.
Mais nous remarquons 2 gros problèmes.. :
1. Consommation excessive de données (pendant 10 minutes l'application consomme plus de 30 Mo même en arrière-plan)
2. La déconnexion intempestive de la prise de courant. Nous sommes obligés de redémarrer l'application pour continuer le chat.
L'architecture utilisée est :
Base de données : MySQL
Serveur Web : Apache
Serveur d'application : serveur propriétaire entièrement développé en NodeJS avec SocketIO.
-- OS : Linux Ubuntu
Nous cherchons quelqu'un qui peut nous aider à résoudre ces problèmes.
I am an expert Android developer with over 7 years experience building Android apps. I have worked on a good and custom NodeJS with SocketIO chat server with Android and iOS apps.
I am interested in working on your project and also available for ongoing development.
Please contact me via chat to discuss the details.
hi
i have been working a lot with stickers lately and developed amazing protocols for saving data over sockets to develop realtime collaborative editors. I have used socketIO with node js to implement snap and locksnap protocols. Disconnects are something that too the longest time to solve, but I already have implemented one solution supporting reconnects at the streams level itself.
let's get in to more details. all i can say is that you should start collecting as many life as possible to figure out the disconnects scenario
-French -----
Salut moi c est Armand
Il vous faut un server de presence avec le protocole XMPP
- XMPP server
- mecanisme de caching des message pour eviter de reloader les message
- aussi mettre des script sur le server linux pour la veille des deamons
n hesiter pas a me contacter je vais resourdre le problem facilement
cordialement
English-----
Hi this is Armand I would like to help you guys on this project
You ll need a to use XMPP protocole reliability
caching the messages on the device
also have some script to check the deamons on the linux server
feel free to contact me we can solve that
also if you interested using firebase that could be also a great Idea
Best