2👍
You might want to take a look at websockets, and especially at websocket.io, that allows you to fall back to comet (comet isn’t going to disappear anytime soon) when native websockets are not available, although as you are targeting the iphone (app?) you can choose whatever you want.
One advantage of using websocket.io is that it includes fallback mechanisms in case a browser does not support websockets (with flash and/or longpolling)
The current state of afairs in djangoland is, independently of the transport mechanism, that django and other mainly wsgi based frameworks aren’t good at comet/websockets. That doesn’t mean you can’t integrate comet/websockets with django, but you normally place another piece of technology in between.
A common implementation is to use something like redis+pubsub and a async server combination like node.js/socket.io or a python framework like twisted, orbited, cyclone, or evserver.
Take a look at these questions that have to do with websockets and django:
- Django/gevent socket.IO with redis pubsub. Where do I put things?
- Can I use Socket.IO with Django?
- Making moves w/ websockets and python / django ( / twisted? )
- Django / Comet (Push): Least of all evils?
some iphone websockets questions I quickly looked up:
- trying to connect to node.js and socket.io 0.7.2 from iphone
- iPhone Objective-C socket communication with Socket.IO
some tutorials/projects that might help with the django side: