On Monday, 1 June 2015 01:42:38 UTC+2, Curtis Maloney wrote:
>
> I think the real questions are:
>
> 1. What is stopping a 3rd party product from providing the features you 
> want?
>

Nothing as far as I see it. Will develop as a third part  
 

> 2. Why should your solution be the "blessed" solution?
>

> The discussion clearly shows there are several ways to skin this cat... 
> why is your way better than any other?  Until there is a clear winner [see 
> migrations and South] it should live as a 3rd party app, with Django 
> providing whatever mechanisms/support it can.
>
> Personally, I've used DOM-SSE to implement a simple chat service in 
> Django, using Redis for the PUB-SUB server.  It was only really feasible 
> because (a) I used gevent, (b) no ORM means no need for async DB adapter, 
> and (c) the py-redis module is Pure Python, so can be monkey patched.
>
> [FYI I've also translated that same code to raw WSGI app, and using 
> async-io, available on github if you're interested </shameless-plug>]
>

There are basically two ways of getting out of the request-response cycle: 
websockets and SSE. Websockets are complicated, and SSEs are easy, with a 
protocol that is similar to what Django already has. So SSEs are clearly a 
better fit with Django. Given that we want to give people a way to do async 
in Django (open for debate, I think so), I think it makes sense to talk 
about the technical implementation.

I would love to see your code, especially if I can compare the two 
versions, and maybe ever write one using the model I'm proposing.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/d465a072-c3de-4258-bf79-cc3e858d4af2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to