dio VS centrifuge-dart

With no release in the last 6 months, piling up of issues and launch of a new fork (diox), I felt something was going on with dio. Sadly, today I came across an official announcement (updated on the project repo 2 days back):

You might want to think twice about dio....we evaluated dio on a recent project and decided to avoid it after running into a blocker when setting a custom timeout (this bug: https://github.com/flutterchina/dio/issues/1454)

- and Dio for http requests

I also had some troubles choosing which Dart HTTP client to use. I've started with dio, but when I tried to read one of our bigger JSON responses (~1.5mb) my browser tab froze (there seems to be an old issue describing the same behavior). After that I've switched to the default dart's http package and it is working fine but it doesn't have builtin requests abort/cancellation.

Connect to it using https://github.com/centrifugal/centrifuge-dart or without any connector library using unidirectional transports: https://centrifugal.dev/docs/transports/overview#unidirectional. For authentication you can pass JWT issued by your Django backend or proxy connection attempt to Django backend ( like shown in this post https://centrifugal.dev/blog/2021/11/04/integrating-with-django-building-chat-application )

Yes. There are clients for bidirectional transports (for example, for Dart/Flutter - https://github.com/centrifugal/centrifuge-dart, and for JS/Swift/Java - so React/Angular/Vue covered, and I never heard what Svelte is but if can use JS libraries then things should work just fine). And it's possible to connect without client libraries if you are using unidirectional transports – just use native browser EventSource object, or use code generation and GRPC to connect to unidirectional GRPC.