Implement CCS for Android push messaging on Google App Engine using python -


i trying implement ccs server side of android application on google app engine. code works fine when hosted on local computer , able send push messages device. when deploy same on gae, throws following errors

2013-08-18 06:54:55.950 / 500 11ms 0kb mozilla/5.0 (macintosh; intel mac os x 10_7_5) applewebkit/537.36 (khtml, gecko) chrome/28.0.1500.95 safari/537.36 106.197.45.136 - - [18/aug/2013:06:54:55 -0700] "get / http/1.1" 500 0 - "mozilla/5.0 (macintosh; intel mac os x 10_7_5) applewebkit/537.36 (khtml, gecko) chrome/28.0.1500.95 safari/537.36" "mad-push.appspot.com" ms=12 cpu_ms=21 app_engine_release=1.8.3 instance=00c61b117c247a73c2df78d7e42f9a5653723e54 e 2013-08-18 06:54:55.941 invalid debugflag given: socket e 2013-08-18 06:54:55.942 debug:  e 2013-08-18 06:54:55.943 debug: debug created /base/data/home/apps/s~mad-push/1.369591069415732344/xmpp/client.py e 2013-08-18 06:54:55.943 debug:  flags defined: socket e 2013-08-18 06:54:55.944 debug: socket       start plugging <xmpp.transports.tcpsocket instance @ 0x10928c88> <xmpp.client.client instance @ 0x10928c10> e 2013-08-18 06:54:55.946 debug: socket       stop  plugging <xmpp.transports.tcpsocket instance @ 0x10928c88> out of <xmpp.client.client instance @ 0x10928c10>. e 2013-08-18 06:54:55.946 client instance has no attribute 'dispatcher' traceback (most recent call last):   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1511, in __call__     rv = self.handle_exception(request, response, e)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1505, in __call__     rv = self.router.dispatch(request, response)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1253, in default_dispatcher     return route.handler_adapter(request, response)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1077, in __call__     return handler.dispatch()   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 547, in dispatch     return self.handle_exception(e, self.app.debug)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 545, in dispatch     return method(*args, **kwargs)   file "/base/data/home/apps/s~mad-push/1.369591069415732344/main.py", line 70, in     auth = client.auth(username, password)   file "/base/data/home/apps/s~mad-push/1.369591069415732344/xmpp/client.py", line 214, in auth     while not self.dispatcher.stream._document_attrs , self.process(1): pass attributeerror: client instance has no attribute 'dispatcher' e 2013-08-18 06:54:55.948 traceback (most recent call last):   file "/base/data/home/runtimes/python27/python27_lib/versions/1/google/appengine/runtime/wsgi.py", line 223, in handle     result = handler(dict(self._environ), self._startresponse)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1519, in __call__     response = self._internal_error(e)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1511, in __call__     rv = self.handle_exception(request, response, e)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1505, in __call__     rv = self.router.dispatch(request, response)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1253, in default_dispatcher     return route.handler_adapter(request, response)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 1077, in __call__     return handler.dispatch()   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 547, in dispatch     return self.handle_exception(e, self.app.debug)   file "/base/data/home/runtimes/python27/python27_lib/versions/third_party/webapp2-2.3/webapp2.py", line 545, in dispatch     return method(*args, **kwargs)   file "/base/data/home/apps/s~mad-push/1.369591069415732344/main.py", line 70, in     auth = client.auth(username, password)   file "/base/data/home/apps/s~mad-push/1.369591069415732344/xmpp/client.py", line 214, in auth     while not self.dispatcher.stream._document_attrs , self.process(1): pass attributeerror: client instance has no attribute 'dispatcher'

please note application on gae contains xmpppy library folder locally. downloaded source code xmpppy.sourceforge.net/

here test code deployed in gae

import webapp2 import sys, json, random, string, xmpp server = 'gcm.googleapis.com' port = 5235 username = 'my app id' password = 'api key' registration_id = 'device registration id'  unacked_messages_quota = 1000 send_queue = []  # return random alphanumerical id def random_id():   rid = ''   x in range(8): rid += random.choice(string.ascii_letters + string.digits)   return rid  def message_callback(session, message):   global unacked_messages_quota   gcm = message.gettags('gcm')   if gcm:     gcm_json = gcm[0].getdata()     msg = json.loads(gcm_json)     if not msg.has_key('message_type'):       # acknowledge incoming message immediately.       send({'to': msg['from'],             'message_type': 'ack',             'message_id': msg['message_id']})       # queue response server.       if msg.has_key('from'):         # send dummy echo response app sent upstream message.         send_queue.append({'to': msg['from'],                            'message_id': random_id(),                            'data': {'pong': 1}})     elif msg['message_type'] == 'ack' or msg['message_type'] == 'nack':       unacked_messages_quota += 1  def send(json_dict):   template = ("<message><gcm xmlns='google:mobile:data'>{1}</gcm></message>")   client.send(xmpp.protocol.message(node=template.format(client.bind.bound[0], json.dumps(json_dict))))  def flush_queued_messages():   global unacked_messages_quota   while len(send_queue) , unacked_messages_quota > 0:     send(send_queue.pop(0))     unacked_messages_quota -= 1    class mainhandler(webapp2.requesthandler):     def get(self):         client = xmpp.client('gcm.googleapis.com', debug=['socket'])         client.connect(server=(server,port), secure=1, use_srv=false)         auth = client.auth(username, password)         if not auth:             self.response.out.write('failed')             sys.exit(1)         client.registerhandler('message', message_callback)         send_queue.append({'to': registration_id,'message_id': 'reg_id','data': {'message_destination': 'regid','message_id': random_id()}})         while true:             client.process(1)             flush_queued_messages()    app = webapp2.wsgiapplication([('/', mainhandler)],debug=true)

as per https://developers.google.com/cloud-messaging/server#role

note google appengine not support connections xmpp (ccs).


-

Popular posts from this blog

php - How should I create my API for mobile applications (Needs Authentication) -

background so i've been researching quite bit past week api's , have been reading concepts , programming one. currently have website programmed in php using popular framework called laravel. website has user database , users able log dashboard on website, works want website side. now next project of business i'm focusing on creating mobile applications (ios & andriod).what need these mobile applications being able login through application ui (not being redirected site callback url) able view , manage dashboard. the method of authentication , authorization want use application go like client asks user login through ui user enters credentials client sends request login api the api checks if credentials correct api creates token stored in token database linked user id api returns 200 ok json response or this { "token" : "ols25usjiay81hdy81", "expiry" : 3/06/2016 14:00} client remembers token , expiry whenever user/c
Read more

5 Reasons to Blog Anonymously (and 5 Reasons Not To)

Image
This guest post is by Phil (not his real name) of somehighschoolblog . It used to be impossible to run a business anonymously. Sure, some authors could pull it off, but if you worked at an office, what were you supposed to do? Go to work with a bag over your head? But today anyone can accomplish this, because anyone can author a blog (and you thought I was going to tell you to work with a mask on, or something). Copyright Ovidiu Iordachi - Fotolia.com Depending on your motives, you may or may not have considered blogging anonymously. You probably didn’t contemplate blogging anonymously if: • your only motivation is to become “famous” • your blog connects to another part of your life • you are blogging to build more connections with your friends or boss. You should consider blogging anonymously if: • you’re planning on touching on a sensitive or taboo subject • you don’t want to be identified with your blog • you are worried about negative real-world consequences that could arise from y
Read more

Google AdWords and AdSense - A Dynamic Small Business Marketing Duo

Unless you have been living under a rock for the last year or so, you probably know that Google has become the king of the search engine hill. There are many reasons for this but number one in my opinion is that above all else they put value on content. Today I want to introduce you to two very powerful small business advertising options created by Google. These two ingenious programs have all but revolutionized the way advertising is done on the web. Warning: If you are thinking..."web advertising isn't for me, I just need a few more clients around the block"...you better read this or be prepared to have your competitors eat your lunch. Goolge AdSense - Again content is king at Google. This program allows web site "publishers" to add some code from Google and receive "content relevant" ads on their site from other site owners. Here is an example - those ads in the box on the right of the page are delivered by Google and are matched to the content
Read more