django-channels VS requests-futures

Channels Medium Article

WebSockets or MQTT. If you’re open to Python and Django as a framework, check out Django Channels.

Creating a PWA is not like playing a card that wins the game. Moreover, users do not yet know the potential or do not know that they can be installed so they have a bit of a hard time catching on. At the moment I use Django + HTMX + AlpineJS to build my applications. This stack allows you to use WebSockets, but HTMX is not yet very mature in this respect. If you aim to create something complex on the user experience side, I have used the Django (+ Django rest framework) + React stack for years. It's good but it takes time both for creating things and to master it. Maybe you want to check out Django Channels too https://github.com/django/channels

Use Django channels package. I'm not very convinced for these reasons:

github issue

One program I sorta like is channels. You may have some luck searching for python example repositories (IIRC there is at least one project like this, with the structure and explaining what each stuff does, give preference to more recent projects as packaging is something that went through a lot of changes in the recent years).

Extra background information: * https://stackoverflow.com/a/49043121/1842286 * https://stackoverflow.com/questions/62199335/django-session-is-not-being-persisted-and-cookie-is-not-being-set-when-using-dja * https://github.com/django/channels/issues/1425 * https://github.com/django/channels/issues/1402 * https://github.com/django/channels/issues/1096

- https://github.com/ross/requests-futures

For the simple one-off case, check out requests-futures or requests-threads

Lately I tried https://github.com/ross/requests-futures and it is really nice little wrapper for requests library that makes it run asynchronous via thread pool. Worth checking out if you are already using requests lib.

requests-futures can handle that

Thank you, I didn’t know about this before. Looks like either requests-threads or requests-futures can do the job. Not sure how I can add async and await to the script above, I’ll tinker around with it later!

I found examples of running parallel async http requests using grequests, but in its GitHub page it recommends using requests-threads or requests-futures instead. Which of them would be the most straightforward tool for optimizing a sequence of GET requests against an API. Case scenario: API endpoint provides paginated responses. With first response, I get the total of itens, which allow me to prepare all the remaining urls. The API allows for 25 simultaneous requests from a single user session (JWT token).

I would suggest using a session in requests if you're not already but also to look at asyncio/aiohttp , requests-futures or requests-html which can be used asynchronously and is written by the author of the requests library.