The basic challenge with any chat application is the long polling bit,
django by default isn't really designed to handle that. Other servers
(Tornado, etc.) are much better at handling the long polling cycle that
typical web chat applications require.
I was just finishing an exploration of Django+Tornado -- building a chat
application -- which I've now pushed up to github.
http://github.com/koblas/django-on-tornado
The only "trick" at the moment is that a response that is returned via
the async Tornado handler isn't passed back up the middleware stack,
pondering good ways to deal with that. But in the mean time, here's a
functional chat application to play with if you're interested.
--koblas
On 8/31/10 4:34 AM, Shamail Tayyab wrote:
> Hi,
>
> I am working on a chat application in Django, how can I ensure that
> I do not have to poll the server for any chat data.
>
> Possible approaches that I've been to:
>
> 1. BAD - use polling.
>
> 2. Use long polling - bad approach afa browser support is concerned.
>
> 3. Using sockets in flash - makes the application flash dependent.
>
> Is there some good way to do this? Or if there is something Django
> specific? Something like HTTPBinding or any 3rd party tested libraries?
> I am expected to provide support till IE6. :-(
>
> Correct me if I am wrong, flash is available on 95% of the systems,
> this approach looks like safest bet, is it good to go?
>
> Btw, how does Gmail and FB chat works?
>
> Thanks
>
> --
> Shamail Tayyab
> Blog: http://shamail.in/blog
>
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment