Web support

[mel-mouk]

Hi,
I really needed web support for one of my projects, so I worked on the implementation.

As the other PR regarding this topic hasn't been updated for a year, I started over, using the last version of everything instead of starting from there.

Here are a few explanations about my choices :

• I first wrote a custom wrapper to avoid introducing a new dependency. But web_socket_channel is pretty light and very well maintained so I thought it made more sense to reuse their work
• I didn't use the userAgent as we cannot use it with dart:html and it works perfectly fine without it. Seems simpler and more consistent that way. If you think it's important to keep it for dart:io, I can write a wrapper similar to the one used in web_socket_channel but able to handle the header parameters (web_socket_channel chose not to handle it in their cross-platform class and conditional import requires a common class with an implementation per platform to compile, that was the issue with the other PR on that topic)

Let me know if you want me to change something

[tanutapi]

Hi Mel-mouk! Thank for your work. At the beginning of the project I used to use the web_socket_channel but for some the reason I replaced it with dart.io. It quite a long time and I can't remember the exact reason. It might be the stability issues on mobile. Could you share does this new implementation work well on your product web/mobile?

We might publish it as a beta version and see if it work well then we publish it again.

Best,

[mel-mouk]

I tested it on MacOS, web and iOS. Working fine on those three platform for me, I don't have the hardware available atm to try on Linux, Windows and Android.

Their scores are pretty good for the last release https://pub.dev/packages/web_socket_channel/score and I'm not aware of any stability issues on the latest versions

[tanutapi]

The package is now live at: https://pub.dev/packages/dart_meteor/versions/4.0.0-beta.1