Re: Daphne behavior question: Application close timeout and caching

hi,

Daphne support both http and websocket connect, if it's an http connection, I think daphne will close the application when the application gives a response. But if it's a websocket connection, it will keep the connection and last until the websocket connect close.

On Wed, Oct 9, 2019 at 7:46 AM DeVonte Applewhite <devonte_applewhite@trimble.com> wrote:

Hello,

I am using Daphne to run a Quart app (https://pgjones.gitlab.io/quart/index.html#) and I wanted to use caching to improve performance.

I looked at the settings for Daphne and have a question about the below option:

  --application-close-timeout APPLICATION_CLOSE_TIMEOUT

                        The number of seconds an ASGI application has to exit

                        after client disconnect before it is killed

Does Daphne launch an application upon receiving a request, then kill it after the application gives a response every time?

If this is the case, I assume in memory caching would not work since the process running the app would be killed after every request.

Can someone give more information on the behavior of Daphne regarding the application close timeout?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7cf9d264-e5f3-4486-98c9-60a891eca48f%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABexzmh99kDHwG71zMHCCOM8nL8%3DAJLub8qmW2zORXbumXWw4Q%40mail.gmail.com.