Thanks Robert! All the options you mention look feasible. Do you (or anyone else on this forum) know the specific limitation that I'm concerned about? How many resource IDs can exist for a single google account in talk.google.com? Is there a talk.google.com limitation, or an XMPP limitation, or both?
I read about C2DM and it looks like a promising alternative, with the only downside that it is supported on Android 2.2 or later only. With Google claiming 29% of the devices out there are still on 2.1 ( http://developer.android.com/resources/dashboard/platform-versions.html), and many may not have an upgrade path, it might be a deal-killer for some. For me, I could probably even use a hybrid approach, where I use XMPP for 2.1 devices, and C2DM for 2.2 devices. On Mon, Mar 28, 2011 at 12:26 PM, Robert Kluin <[email protected]>wrote: > Maybe you could get something working with the Channel API? You might > want to star issue 4189 (or 4266), to enable other clients in > additional to js. > > http://code.google.com/p/googleappengine/issues/detail?id=4189 > http://code.google.com/p/googleappengine/issues/detail?id=4226 > > > You might also look into: > http://urbanairship.com/ > http://code.google.com/android/c2dm/index.html > > > > Robert > > > > > > On Mon, Mar 28, 2011 at 10:10, Rishi Arora <[email protected]> > wrote: > > Is there any limit to the maximum number of google talk clients that can > > login using the same gmail account (but using different JID resource > IDs?). > > Can this number of clients be as large as 100k? > > I'm implementing an android app which has a server component implemented > in > > python on GAE. One of the features involves generating notifications on > the > > android app triggered by updates from the GAE app. After looking at > several > > options, I elected to use XMPP and talk.google.com server for generating > > messages from the GAE app, destined for the android app. The GAE app > engine > > runs a cron job periodically, and sends messages to android app users > when > > they are online. On the android side, I did not want to have the user > input > > their username and password when using my app (they may not be > comfortable > > in doing that). So, I created a generic gmail account, and I hard-code > its > > username and password in the android app. So the android app signs in > into > > talk.google.com as "[email protected]", but it uses a unique > > resource ID when invoking the xmpp.login() API. The unique resource ID > is > > in fact the users's gmail address. On the GAE app side, when the app > needs > > to direct a message to a single user, it directs it to the JID > > [email protected]/<user's_email>, in the hope that only the > android > > app with the resource ID matching the user's email will receive that > > message. In my testing, this is working just fine - with a couple of > > android devices. But I am concerned that I might run into a limitation > with > > the maximum number of resource IDs permitted for a given gmail user. For > > instance, can my generic gmail user, [email protected] have > 100k > > resource IDs associated with it, all logged in simultaneously? Sounds > not > > very reasonable. My alternative is to use the android app user's gmail > > account, but then I'll have to settle to asking the user to input their > > username and password. That means my app will have access to their > username > > and password. And that may sound like a big security risk to users. > > Another alternative is to host my own jabber server. I'm not sure if > GAE's > > xmpp api will allow me to connect to it. Although, what I could do is, > have > > my GAE app talk to my self-hosted jabber server through google talk. My > > jabber server will login to talk.google.com as a jabber client, to > > communicate with the GAE app. And all android app users will log in to > my > > jabber server with whatever username/password I see fit. > > Any thoughts anyone? > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
