views:

86

answers:

4

Hi!

I'm currently writing an Android app that should be able to communicate in real time with another app hosted in Google's app engine. Since I can't use sockets in GAE, I though maybe using XMPP over GTalk server would solve my problem. But that way the Android app would be connected to the users account and thus showing the user as being online, when in reality the user is not.

Any way of achieving this kind of communication without showing the user as being online? Or any alternatives?

Thanks!

A: 

Not sure about the exact requirement of your app, but.. perhaps C2DM can be an alternative?
http://code.google.com/android/c2dm

mas
One of my objectives is to make the app functional to older versions of android, and afaik C2DM it's currently only available to Android 2.2...I've already considered other options like the MQTT protocol (http://tokudu.com/2010/how-to-implement-push-notifications-for-android/) or building my own application server, but I can't afford a server that would have to be always-on to serve my application...
TomS
+1  A: 

May be you can use the channel API http://goo.gl/QNPc

sahid
It seems like a good solution, but isn't it still inactive on the production server?
TomS
I think its activated because the demo is online: http://io-trivia-quiz.appspot.com/
sahid
TomS
A: 

Why are you shying away from HTTP/JSON? Might be useful to know why you discounted the obvious solution...

Cloudbreak NZ
I have to admit, I'm not really familiar with JSON. But after a little research it looks like JSON it's a lightweight XML alternative... Also, making HTTP requests and getting the responses won't to because sometimes the server response won't be ready right away, timing out the connection. What I am missing here? :s
TomS
A: 

I've found the PubNub service (http://www.pubnub.com/).
It enables push notifications through API's on several platforms (PHP, Ruby, JavaScript, Java, ...).
It's a paid service, but provides a free daily quota.

Although it's not the ideal solution to my problem, it'll have to suffice until some Channel API documentation comes out.

Thanks to all of you!

TomS