Hi Harri Smatt, Sender Id needs to be in the App to register with GCM server and get the GCM ID. I believe you are referring to GCM API key.
We will be encrypting the GCM API Key in our app. On top of that we will be using DexGuard to obfuscate the code. And more over sending message to GCM is an *HTTPS *call. Considering all the above, we think that it should be secure enough. Thanks a lot for your reply. Do you foresee any other issues? Varun On Tuesday, 8 July 2014 22:24:17 UTC+5:30, Harri Smatt wrote: > > > On 7 Jul 2014, at 16:38, MS <ms.jack...@gmail.com <javascript:>> wrote: > > Are we missing anything by not choosing to push via our own server? > > Is following such an implementation correct? > > > Guess it works - but isn’t it any concern to you that you need to bundle > your Sender Id, usually stored only on 3rd party application server, within > the application? > > And, well, can’t tell how Google reacts once their GCM server gets > hammered from millions, if not trillions, different IPs with your Sender Id. > > — > H > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
