requests-threads VS pusher-js

- https://github.com/requests/requests-threads

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

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).

Serveless Websocket service

if you are on time, since it is a coursework, and it is allowed to use some libraries, you can check how to use pusher it should be fairly easy for you too integrate to your application.

I've built a flutter web chat using flutter_chat_ui and dart_pusher_channels, for the backend I used soketi which is an open source node.js pusher replacement but you could just use pusher.com if you can squeeze into their free tier.

What? No. Takes 5-10 minutes to set up a websocket server manually or is just requires a few configuration variables to be set if using a hosted service like Pusher.

Pusher is used for real-time communication. So you want to update the user's status in the admin panel, without reloading the page. That is no PHP question, but it might be PHP related (because you might want to trigger something with PHP upon update).

Personally I use pusher for this purpose, I send events from the SvelteKit backend whenever I'm communicating with my database. Then in the client I listen to those events to update the UI when needed.

Pusher for most chat messages and real-time notifications

Just wanted to give everyone a heads up, Caches will be down for around an hour later today. I am going to go ahead push the beta test version of the end-to-end encrypted private messaging feature to the production box. I think it's mostly ready but I would like others to use it and provide feedback. It uses the pusher API, so now all Caches PM's will be end-to-end encrypted! Nothing stored with me or Pusher, just clean, no hormone, no antibiotic, all natural private messaging.

socket.io would handle the fallbacks. Implement sticky session, only relying on websocket is a poor decision choice even in 2022. Alternatively, you can look into Pusher which basically provides socket as a service

Pusher API account, you can create one here Pusher account