I'm trying to implement a globalized Socket.io connection method for an entire
application (multiple activities).
The requirements:
1. The socket.io must be enabled as long as the user is logged into the
application
2. The socket has to keep connected even when switching activities.
3. The
What do you mean that moving calls to a device didn't work? That is most
likely what you want. I would implement it as a started and bound service.
On Wed, Jan 20, 2016, 3:21 PM Gabriel Avila wrote:
> I'm trying to implement a globalized Socket.io connection method for an
>
By that I meant that the socket.io methods were moved from the application
extended class into an android service class but I still kept getting
multiple "hits" to the socket.io "on" methods regardless on the service
thread being executed only once.
On Wed, Jan 20, 2016 at 5:31 PM, Justin
3 matches
Mail list logo