Last post Nov 30, 2015 09:51 AM by florin.nitulescu
Nov 30, 2015 07:39 AM|florin.nitulescu|LINK
Do you think it is possible to make a new ClientTransport implementation that uses Google Cloud Messaging (GCM) Cloud Connection Server (CCS), which is an XMPP endpoint, for transmitting messages back and forth between server and Android clients?
The application I'm developing it's from the chat application type. But the Android platform makes it very hard for someone to keep a web-socket connection open for a long time. The device goes to sleep, the connection it's lost, and you get notified too late.
If you keep the device awake enough to process every incoming keep-alive from the signalr server (not all the time, only when the keep-alive is received), the battery usage becomes pretty high. Then you have to deal with their recently introduced "doze and
standby modes". The problem becomes a lot more complex.
It would be much easier if I had a "transport" for my mobile clients that hides this complexity from me using GCM CCS XMPP endpoint and I can continue enjoying life with SignalR.
Do you think it is possible to introduce this on your todo list for SignalR?
Nov 30, 2015 08:32 AM|Mikesdotnetting|LINK
You should post feature requests for SignalR to its Github repository as an issue: https://github.com/SignalR/SignalR
Nov 30, 2015 09:51 AM|florin.nitulescu|LINK
I tried first submitting an issue on GitHub, but in their guidance (https://github.com/SignalR/SignalR/blob/master/CONTRIBUTING.md) they say that issues are only for bugs. However
I will post a feature request as an issue on GitHub and I will come here with the updates.