You are right. Whether you use GCM to send the payload depends on how much data there is to be sent and whether the client actually needs the data or not. This would be a design decision for your application. The demo app in the video sends the ID of the Note object - instead it could have sent just a ping saying that "some data has changed", and the client could have performed an incremental sync based on the previous sync time - this would guarantee that the client is in a consistent state.
The first half of the preso was about using Google APIs - tips on using proguard to reduce app size, how to do do auth etc. "Web APIs" is used in a general sense to refer to Google APIs and Cloud Endpoints. Hope that helps and apologies for the confusion.
GCM is not meant to transfer the actual data - you will need to make an API call to fetch the updated data. GCM essentially sends a ping to the devices to say that the data has changed.
Maybe I'm not understanding something, but the GCM website says "This could be a lightweight message telling the Android application that there is new data to be fetched from the server (for instance, a movie uploaded by a friend), or it could be a message containing up to 4kb of payload data (so apps like instant messaging can consume the message directly). "
Doesn't seem realistic to use GCM to communicate with the app in the way mentioned in this session - the GCM provides no guarantee for delivery time or sequence.
Does anybody know how can I get the Demo Code of this session or Building Mobile AppEngine backends? Only demo codes for the Brad Adams session is there..
I'm disappointed by this session. I expected tips and tricks for communicating with web api's as suggested in the title. Instead its an introduction to google cloud end points. Really disappointed, please change the title from "Web api's" to "google cloud end points".
You are right. Whether you use GCM to send the payload depends on how much data there is to be sent and whether the client actually needs the data or not. This would be a design decision for your application. The demo app in the video sends the ID of the Note object - instead it could have sent just a ping saying that "some data has changed", and the client could have performed an incremental sync based on the previous sync time - this would guarantee that the client is in a consistent state.
The first half of the preso was about using Google APIs - tips on using proguard to reduce app size, how to do do auth etc. "Web APIs" is used in a general sense to refer to Google APIs and Cloud Endpoints. Hope that helps and apologies for the confusion.
GCM is not meant to transfer the actual data - you will need to make an API call to fetch the updated data. GCM essentially sends a ping to the devices to say that the data has changed.
Maybe I'm not understanding something, but the GCM website says "This could be a lightweight message telling the Android application that there is new data to be fetched from the server (for instance, a movie uploaded by a friend), or it could be a message containing up to 4kb of payload data (so apps like instant messaging can consume the message directly). "
Doesn't seem realistic to use GCM to communicate with the app in the way mentioned in this session - the GCM provides no guarantee for delivery time or sequence.
We have an issue with "Generate App Engine Backend" on the Windows environment - we are working on this and should release a fix for it soon.
Does anybody know how can I get the Demo Code of this session or Building Mobile AppEngine backends? Only demo codes for the Brad Adams session is there..
Great Presentation!
Try Eclipse 3.7 I had the same problem with 4.2
Does anyone know where I can get the source code please?
hmm strange that the apps genies are using apple ??? wierd
just use eclipse 3.7
I'm disappointed by this session. I expected tips and tricks for communicating with web api's as suggested in the title. Instead its an introduction to google cloud end points. Really disappointed, please change the title from "Web api's" to "google cloud end points".
It is fixed!