For questions about using Django, please use the django-users mailing list.
This list is for the development of Django itself.
On Thu, Jun 8, 2017 at 12:21 PM, Matheus Fernandes <
matheus.souza.fernan...@gmail.com> wrote:
> Hi!
>
> It's the first time that I'm developing a real-time application.
Hi!
It's the first time that I'm developing a real-time application...
A few days ago the application received more accesses than the usual and
started to return a 503 (full queue) error.
How can I handle this error?
For now I cleaned my redis instance ("redis-cli flushall")
Thanks :)
--
You
A pull request is available for review:
https://github.com/django/django/pull/8610
I don't have any experience writing responsive CSS so reviews from experts
in that area would be welcome.
On Tuesday, May 30, 2017 at 4:04:51 AM UTC-4, Óscar M. Lage wrote:
>
> Nice suggestion!, imho something li
My thoughts are the same as Shai's below.
On Monday, May 29, 2017 at 4:00:09 PM UTC-4, Shai Berger wrote:
>
> If I understand things correctly, registration of new url-schemas to
> enable
> something like dj-database-url to support 3rd parties should be a trivial
> matter; just add an entry to
Hi everyone,
asgi_rabbitmq is Channels layer on top of RabbitMQ. It was originally
developed as part of Mozilla funding program.
I've complete few major milestones after this. Now it's used in few
production systems. It implements the ASGI specification exactly and
performs well.
I want to
Hi everyone,
asgi_rabbitmq is Channels layer on top of RabbitMQ. It was originally
developed as part of Mozilla funding program.
I've complete few major milestones after this. Now it's used in few
production systems. It implements the ASGI specification exactly and
performs well.
I want to
On Thu, Jun 8, 2017 at 8:55 PM, Tom Christie wrote:
> > Any interface like this would literally just be "this function gets
> called with every event, but you can't listen for events on your own"
>
> Gotcha, yes. Although that wouldn't be the case with asyncio frameworks,
> since the channel read
> Any interface like this would literally just be "this function gets
called with every event, but you can't listen for events on your own"
Gotcha, yes. Although that wouldn't be the case with asyncio frameworks,
since the channel reader would be a coroutine.
Which makes for interesting design t
On Wed, Jun 7, 2017 at 7:05 PM, Tom Christie wrote:
> Making some more progress - https://github.com/tomchristie/uvicorn
> I'll look into adding streaming HTTP request bodies next, and then into
> adding a websocket protocol.
>
> I see that the consumer interface is part of the channels API refer
