This question was answered in the Channels issue
tracker: https://github.com/django/channels/issues/713
On Sunday, July 30, 2017 at 2:55:37 PM UTC+3, Александр Великий wrote:
>
> Hi,
>
> I'm trying to find the way to do the following thing:
>
> When I get websocket message from client, I want to
Hi Tom,
I want to experiment with a uvicorn approach. I planning to do some after
PoC of worker separation from channels. I will let you know if I have some
questions. **Probably** Channels as a library will be a first user of the
suggested interface of the uvicorn.
Regards, Artem.
On Fri, Jul 2
I need python process stdout with debug enabled.
On Wednesday, July 19, 2017 at 7:36:45 PM UTC+3, Shubham Aggarwal wrote:
>
> I am working on ordering system and using django-channels for sending a
> notification to an admin about the order has been placed and it works only
> with 1-2 orders per
d then shuffling data over to the
> caller of receive() using queues etc.
>
> Andrew
>
> On Wed, Jul 12, 2017 at 10:50 AM, Artem Malyshev > wrote:
>
>> Hi,
>>
>> I know we discussed it in private. But I want to bring some ideas in
>> public.
>>
Hi,
I know we discussed it in private. But I want to bring some ideas in public.
During asgi_rabbitmq implementation I notice that channel workers are
coupled to much to the polling of the channel layer. I want to try a
different approach when layer can decide on its own when the message
arriv
e is more feedback from Django core about this; I've not heard
>>> anyone's opinion but mine, and I am not entirely sure if we should do this
>>> (I am also not entirely sure asgi_ipc should be a Django project some days).
>>>
>>> Andrew
>&g
> (they would not have to be existing core, but would need some history of
> open-source maintenance)
>
> The other thing would be to see the existing code have more comments and
> documentation; currently it has very few comments, in particular.
>
> Andrew
>
&g
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
Yes, I saw your changes after I wrote my previous email.
Global capacity for process sounds reasonable. Probably we should state it in
spec.
Regards, Artem.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group
Hi everyone,
It can be huge improvement for asgi_rabbitmq layer. But I'm asking
you to keep this change in the experimental branch before I implement
it for RabbitMQ layer. More questions can came up in progress.
For me it is still unclear how to implement `channels_capacity` option
for differe
Hi everyone,
I'm happy to announce RabbitMQ channel layer for Django Channels!
During last month an a half I'm developing this library and achieve some
meaningful results. I hope you will find this library interesting and will
give it a try.
You can find released package on PyPI:
https:/
Hi everyone,
I'm happy to announce RabbitMQ channel layer for Django Channels!
During last month an a half I'm developing this library and achieve some
meaningful results. I hope you will find this library interesting and will
give it a try.
You can find released package on PyPI:
https:/
13 matches
Mail list logo
